Sorry that my English is not good.
I use this: https://github.com/playdog-io/healthy-ipolef-PQMM established a dapp in my VPS, and it's running at the VPS' localhost:5000. I want to use my local computer to visit the dapp, so I visit (the IP of my VPS):5000, but it didn't work. So can anyone tell me how to make it works?
the VPS is from vultr.
Related
I've worked on my web app and now it's ready to go on production. For developmnent I used XAMPP on my local machine. I need to deploy the app on a Windows Server 2016 in which other people have access to.
So let's start with some question for you!
1:
I suppose that using XAMPP is not a good idea since it doesn't offer a good level of security.
I want to protect my database, my database storage folders and I want to avoid other people to access any part of my environment.
So I actually want to ask you any suggestion on how to deploy my web app avoiding security issues.
I also would like to ask you the better free local environment I can use for production (something like XAMPP but with improved security).
Keep in mind that my web app should only be visible to the local network.
2:
Is there a way I can set an hostname for my server in order to make everyone who is connected to the lan able to reach my server with that hostname? Writing the IP with the port isn't good for user experience. I know I can use the "name" of the computer itself, but setting a custom hostname would be better.
3:
How should I serve the application? Running the normal command "php artisan serve"? Anyway that way just closing the terminal would result in killing the process so the server will become unavailable.
ANY suggestion would be really appreciated. Is my first approach to deployment so I'm really sorry if my questions are stupid.
Thank you in advance!
I have developed a website using XAMPP, and am having issues with being able to deploy it for use. The main issue I am having is that the server I am operating on is a corporate server, so I cannot configure the router for a static IP address. The goal of this website is to have it accessible by 10 different computers that will write to an access database. What would be the best method to accomplish this? Thanks, any suggestions are greatly appreciated as I am about to lose my mind.
about 6 months ago I got into coding, and I've always wanted to start my own game just for fun on the side.
I have wampserver on my computer, and was wondering if that server could publicly host things on the internet?
You need to:
Make sure your server is available on the internet. If you have a router or firewall you may need to open it up.
If you want to have a domain name you need to register that.
If your ISP can give you a static IP address then ask for that.
Whether you have a static IP or a dynamic one then you can use a service such as DynDNS to link the domain name to the IP address.
Yes, you can use your WAMPserver to allow people to publicly access your site.
From some quick googling, I didn't find any instructions, just that it was possible.
I just put a wamp server up on a box in my house just for funsies.
Here is a wampserver forum post with links to the info you seek.
Here is the basic rundown though:
Open up your router to port 80 and forward it to the box you are serving on.
Get setup on a DNS server, I used freedns.afraid.org.
In wamp you are gonna set apache to use virtual hosts (this is in the link).
After that you should be cool.
I bought a VPS a few days back and had a domain name registered. It gave me 2 nameservers.
I only have shell access (no Cpanel/WHM) and it's running CentOS 5. I can visit my site with http://IP/ but not with http://domain.com. What changes do I need to make so that I can visit my site with http://domain.com. I'm really new at this and any help would be greatly appreciated. Thanks.
If you follow the guides that Slicehost provides you will be up and running in no time. In particular, you need to configure your server, install an appropriate web server, and configure it for your domain(s). Visit http://articles.slicehost.com/centos and follow the steps listed.
I have a strange problem, I just installed my php web site on a shared hosting, all services were working fine. But after configuring my app I just could visit my web site only once, other attempts gives:
"The server is taking too long to respond.".
But from other IP i can access, but only once, it seems all ip addressess beeing blocked after first visit(even ftp and other services get down, no access at all from the IP), can anyone help to explore this problem ? I don't think that it's my app problem, the app works fine on my local PC.
Thanks.
First thing to try would be a traceroute to determine where your traffic is being blocked.
In a windows command prompt:
tracert www.yoursharedhostingserver.com
At the moment, trying to access this address gives this:
Fatal error: Class 'mainController'
not found in
/home/myicms/public_html/core/application/crApplication.class.php
on line 181
I have tried it multiple times and it didn't block me. It might be that You have already solved this problem.
As far as I know, the behavior described by You could only be explained by a badly configured intelligent firewall. It may have been misconfigured by Your host.
If You visit a site at a certain host and suddenly You cannot access an ftp on this host, then it's either a (really bad) firewall or a (very mean) site that explicitly adds a firewall rule to ignore that address.
Some things that You might look into:
It might be something with identd too. What was the service You have configured on Your host? Was it by any chance any kind of server-controll panel (that might have an ability to controll a firewall)?
Is the blockade permanent, or does it go off after 24h, or does it only go off after rebooting the server? Does restarting some services makes the blockade go off?
Did You install any software that "protects Your server from portscanning"? It might be a bit too aggressive.
I wish You good luck in finding a source of this problem!
Chances are that if you can access it once that its actually working. The problem is more than likely in the php code than in the server.