I have just moved to a VPS server. I have uploaded my files to httpdcos/ but then when I access my website, it still shows the server default page.
How do I fix this?
My website is at 216.87.168.104 - the server runs Parallels Plesk.
It happens because apache doesn't serves your website on IP to which your domain name resolved.
Check IP of your domain:
nslookup <yourdomain.tld>
Check output of apachectl -S - make sure that domain name is served on resolved IP address
Related
I am able to access the link http://localhost/men/tops-men/jackets-men.html successfully from my VM (configured using X2Go client).
IP Address of the VM: 10.146.106.204
I am also able to ping the VM successfully from my host machine (Windows).
The page that I am trying to access is a php page deployed on Apache Web Server.
However I am not able to do so from my Windows host machine.
I tried http://10.146.106.204/men/tops-men/jackets-men.html from my Windows machine but it did not work.
Do I have to configure something on my host machine or on my VM ?
Not sure what I am missing.
On VM check you can view http://10.146.106.204/men/tops-men/jackets-men.html
If not you need to configure the web server to listen on that IP (if you're running IIS this is under "bindings" in the right-hand side panel of IIS Manager).
On Host open a cmd window and check you can ping 10.146.106.204
If not check your firewall settings on the VM.
If neither of these 2 things help then you need to add more information about your setup to the question. Those are 2 very simple things you can do to diagnose 2 basic problems you might be having.
I was finally able to solve the problem based on this SO link: Unable to access magento site from anywhere but localhost
Updated the DB table core_config_data and updated the data by replacing http://localhost with http://ip-of-vm and then restarted the apache web server.
I have hosted a site on iis manager and access it locally,but when i access the site on another machine it is giving the error that the server was taking too long to respond.So any suggestion for this that could help me out.
When your other machine is on LAN, you'll have to edit the Hosts file of each computer and add your domain name's entry resolving IIS web server IP address.Thus all LAN systems will know to which IP address to send the request to when your website is browsed.
Hosts file is located at path: C:\Windows\system32\drivers\etc\hosts
I just registered a new domain name and set it to point to an AWS EC2 instance. When I enter the domain name, it loads fine, but then as soon as the page loads, the browser address text is updated to show the ip address (replaces the domain name). I cloned this EC2 from another server where this was not happening and where I hadn't done any non-default Apache2 server settings other than URL shortening to remove .html and .php file extensions. Any ideas what could be happening here? I tried it on multiple computers and multiple browsers.
Sounds like your webserver is issuing a redirect after the first connection is made, and the redirect is pointed to the IP adress of the server. You can get more information to confirm this by using Chrome Network Console.
In this case I had mistakenly updated the DNS record for forwarding rather than for the # tag, so it was forwarding to the site.
I am running an instance of GeoServer on a linux server and I am trying to access the admin page on a separate machine. Is there a way for me to change the address so that I can access it through a browser?
Just figured it out, find the jetty.xml and search for localhost. Change localhost to your IP address of the server. Then change the firewall settings to allow port 8080, I followed these instructions
I am trying to access Sonar through web browser. I already started it on my terminal but when I try to access it on web browser through , it shows nothing. However, the status shows Sonar is running. How can I make it running on the web browser ?
The configuration for Sonar web is:
sonar.web.host=127.0.0.1
sonar.web.context=/sonar
sonar.web.port=9000
sonar.web.host=127.0.0.1
I think this is the problematic line in your conf. This line indicates which IP address the Web Server will bind to. If you set it to 127.0.0.1, then Server will only respond if you reach to it through the IP 127.0.0.1, that is, you'll only be able to access it from localhost, though IPv4. (Your browser will probably prefer IPv6, with ::1 being the host)
Comment out the line (prepending a #) in order to have it listen to every IP the machine is called by.
If you can verify access from the host machine itself, but the above doesn't help, then you might want to check if your firewall is blocking requests.
With the settings you provided, make sure you're using this URL and trying to access the server from the same box: http://127.0.0.1:9000/sonar/
If you're attempting to reach http://127.0.0.1:9000/ and getting the empty page, it's due to the sonar.web.context value you're using.
Note: unless you're hosting SonarQube in an external webserver, you don't need to set the sonar.web.context, in which case, you would just go to http://127.0.0.1:9000/
If this URL isn't working for you, I would suggest looking at the SonarQube server logs in the /logs folder to determine if there were any errors starting the server. If so, you'll want to update this posting with the details from the log, including which operating system you're running.