WebDomains do not serve

Community Support Web
1

I can ping the domains to the website, panel etc. But for some reason i cannot access the sites. Apache2 is online, Nginx is stuck on old IP and does not work.

I think it is Nginx, how do i go ahead on changing the old IP as hestiaCP did not automatically do this?

I changed the IP of the vps, and now it does not work. When i try to restart nginx it says

an 10 15:58:42 web-de-1 systemd[1]: Starting nginx - high performance web server…
Jan 10 15:58:42 web-de-1 nginx[164575]: nginx: [emerg] bind() to 178.63.197.251:80 failed (99: Cannot assign requested address)
Jan 10 15:58:42 web-de-1 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Jan 10 15:58:42 web-de-1 systemd[1]: nginx.service: Failed with result ‘exit-code’.
Jan 10 15:58:42 web-de-1 systemd[1]: Failed to start nginx - high performance web server.

And I have also changed IP for all web domains and removed the old IP from settings.

2

Did you use the command v-update-sys-ip to change the ip?

You can use this command to check the files that are still using the old ip:

grep -RF 178.63.197.251 /etc/nginx/
1 Like
3

I have also ran this command v-update-sys-ip, but it still not changed automatically.

4

I have changed the IP, Nginx is now working, but the sites cannot be loaded but has Internal Server Error.

5

You must check the logs to view the actual error. For the example.net domain, the log should be located at /var/log/apache2/domains/example.net.error.log

1 Like
6

upstream timed out (110: Connection timed out) while connecting to upstream

Thats the error i got, I restarted vps and restarted the PHP-FPM as others had the same issue, but thats all error i got.

7

Check whether apache2 is using the old ip:

grep -RF 178.63.197.251 /etc/apache2/
8

etc/apache2/mods-available/remoteip.conf: RemoteIPInternalProxy 178.63.197.251

9

Replace it with the actual ip and restart apache2.

10

It works now thank you so much :3

1 Like