Internal Error 500 after changing IP

1

Hello,

I change server ip via these comands:

  1. v-update-sys-ip
  2. v-rebuild-users
  3. delete old IP from nginx and apache2
  4. v-update-letsencrypt-ssl

But after that I got Apache2 internal error 500.

How can I resolve problem?

2

What is the exact error? The you check the error logs?

3 
[Wed Nov 29 14:56:15.049624 2023] [mpm_event:notice] [pid 60398:tid 140116223368128] AH00493: SIGUSR1 received. Doing graceful restart

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using maxwell.ofavo.com. Set the 'ServerName' directive globally to suppress this message

[Wed Nov 29 14:56:15.291895 2023] [ssl:warn] [pid 60398:tid 140116223368128] AH01909: 94.237.94.182:443:0 server certificate does NOT include an ID which matches the server name

[Wed Nov 29 14:56:15.298380 2023] [mpm_event:notice] [pid 60398:tid 140116223368128] AH00489: Apache/2.4.57 (Debian) OpenSSL/3.0.11 mod_fcgid/2.3.9 mod_wsgi/4.9.4 Python/3.11 configured -- resuming normal operations

[Wed Nov 29 14:56:15.298419 2023] [core:notice] [pid 60398:tid 140116223368128] AH00094: Command line: '/usr/sbin/apache2'

[Wed Nov 29 14:59:18.337741 2023] [mpm_event:notice] [pid 60398:tid 140116223368128] AH00492: caught SIGWINCH, shutting down gracefully

[Wed Nov 29 14:59:18.719968 2023] [ssl:warn] [pid 67283:tid 140019992300480] AH01909: 94.237.94.182:443:0 server certificate does NOT include an ID which matches the server name

[Wed Nov 29 14:59:18.720276 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity for Apache/2.9.7 (http://www.modsecurity.org/) configured.

[Wed Nov 29 14:59:18.720282 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: APR compiled version="1.7.2"; loaded version="1.7.2"

[Wed Nov 29 14:59:18.720287 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: PCRE2 compiled version="10.42 "; loaded version="10.42 2022-12-11"

[Wed Nov 29 14:59:18.720309 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: LUA compiled version="Lua 5.1"

[Wed Nov 29 14:59:18.720311 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: YAJL compiled version="2.1.0"

[Wed Nov 29 14:59:18.720313 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: LIBXML compiled version="2.9.14"

[Wed Nov 29 14:59:18.720315 2023] [security2:notice] [pid 67283:tid 140019992300480] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.

[Wed Nov 29 14:59:18.720946 2023] [suexec:notice] [pid 67283:tid 140019992300480] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)

[Wed Nov 29 14:59:18.907471 2023] [ssl:warn] [pid 67284:tid 140019992300480] AH01909: 94.237.94.182:443:0 server certificate does NOT include an ID which matches the server name

[Wed Nov 29 14:59:18.917461 2023] [mpm_event:notice] [pid 67284:tid 140019992300480] AH00489: Apache/2.4.57 (Debian) OpenSSL/3.0.11 mod_fcgid/2.3.9 mod_wsgi/4.9.4 Python/3.11 configured -- resuming normal operations

[Wed Nov 29 14:59:18.917508 2023] [core:notice] [pid 67284:tid 140019992300480] AH00094: Command line: '/usr/sbin/apache2'

[Wed Nov 29 15:02:35.029319 2023] [mpm_event:notice] [pid 67284:tid 140019992300480] AH00492: caught SIGWINCH, shutting down gracefully

[Wed Nov 29 15:02:51.463504 2023] [ssl:warn] [pid 896:tid 140510424800192] AH01909: 94.237.94.182:443:0 server certificate does NOT include an ID which matches the server name

[Wed Nov 29 15:02:51.464591 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity for Apache/2.9.7 (http://www.modsecurity.org/) configured.

[Wed Nov 29 15:02:51.464602 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: APR compiled version="1.7.2"; loaded version="1.7.2"

[Wed Nov 29 15:02:51.464607 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: PCRE2 compiled version="10.42 "; loaded version="10.42 2022-12-11"

[Wed Nov 29 15:02:51.464611 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: LUA compiled version="Lua 5.1"

[Wed Nov 29 15:02:51.464613 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: YAJL compiled version="2.1.0"

[Wed Nov 29 15:02:51.464617 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: LIBXML compiled version="2.9.14"

[Wed Nov 29 15:02:51.464619 2023] [security2:notice] [pid 896:tid 140510424800192] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.

[Wed Nov 29 15:02:51.466035 2023] [suexec:notice] [pid 896:tid 140510424800192] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)

[Wed Nov 29 15:02:51.690914 2023] [ssl:warn] [pid 1000:tid 140510424800192] AH01909: 94.237.94.182:443:0 server certificate does NOT include an ID which matches the server name

[Wed Nov 29 15:02:51.699253 2023] [mpm_event:notice] [pid 1000:tid 140510424800192] AH00489: Apache/2.4.57 (Debian) OpenSSL/3.0.11 mod_fcgid/2.3.9 mod_wsgi/4.9.4 Python/3.11 configured -- resuming normal operations

[Wed Nov 29 15:02:51.699283 2023] [core:notice] [pid 1000:tid 140510424800192] AH00094: Command line: '/usr/sbin/apache2'
4

And the website logs?

5 
[Wed Nov 29 09:42:34.052542 2023] [proxy_fcgi:error] [pid 196349:tid 139855182939840] [client 156.240.111.18:0] AH01071: Got error 'Primary script unknown'

2023/11/29 15:13:56 [error] 940#940: *910 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.70.15.24, server: ofavo.com, request: "GET / HTTP/2.0", upstream: "https://94.237.94.182:8443/", host: "ofavo.com"

2023/11/29 15:13:57 [error] 940#940: *918 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.70.15.24, server: ofavo.com, request: "GET / HTTP/2.0", upstream: "https://94.237.94.182:8443/", host: "www.ofavo.com"
6

Is 172.70.15.24 the old ip?

In that case rebuild the web-domains / mail domains aswell

7

Hello! I have same problem.
apache log:

2024/04/27 16:50:36 [error] 86014#86014: *57 upstream timed out (110: Connection timed out) while connecting to upstream, client: 192.168.0.145, server: site.local.my, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.0.145:8080/favicon.ico", host: "site.local.my", referrer: "http://site.local.my/"
2024/04/27 16:50:47 [error] 86014#86014: *59 upstream timed out (110: Connection timed out) while connecting to upstream, client: 192.168.0.145, server: site.local.my, request: "GET / HTTP/1.1", upstream: "http://192.168.0.145:8080/", host: "site.local.my"
2024/04/27 16:51:17 [error] 86014#86014: *59 upstream timed out (110: Connection timed out) while connecting to upstream, client: 192.168.0.145, server: site.local.my, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.0.145:8080/favicon.ico", host: "site.local.my", referrer: "http://site.local.my/"

192.168.0.145 - new IP

Can anybody help?

8

After making the changes restart the apache server to make the changes apply.

9

I restart nginx , apache, laptop after command v-update-sys-ip. Not working.

Nestia - installed on my laptop for local develop. If i connected to access point and IP is 192.168.1.106 it`s worked. If i connect to another access point where ip 192.168.0.145 or 192.168.52.62 i have

[error] 940#940: *918 upstream timed out (110: Connection timed out) while connecting to upstream,

I am desperate :hot_face: