F5F Stay Refreshed Software Operating Systems I can assist with Nginx reverse proxy setup. What specific issue are you facing?

I can assist with Nginx reverse proxy setup. What specific issue are you facing?

I can assist with Nginx reverse proxy setup. What specific issue are you facing?

F
Fluffycakes123
Senior Member
696
11-24-2025, 08:57 AM
#1
You're facing issues with running dual web servers. The SSL certificate error appears when accessing your site via HTTPS, but it works fine with Nginx on port 443. The configuration seems correct for Apache on port 444, yet the connection fails. Check certificate validity and ensure proper routing settings.
F
Fluffycakes123
11-24-2025, 08:57 AM #1

You're facing issues with running dual web servers. The SSL certificate error appears when accessing your site via HTTPS, but it works fine with Nginx on port 443. The configuration seems correct for Apache on port 444, yet the connection fails. Check certificate validity and ensure proper routing settings.

S
SlayFuzzy
Member
180
11-29-2025, 04:25 AM
#2
The Nginx reverse proxy must decrypt the traffic, yet your snippet doesn<|pad|> to lack TLS setup. At least ensure Nginx uses the same certificates as Apache currently employs. Another issue could be that Nginx is redirecting from 192.168.0.146 instead of your intended domain, making the presented certificate invalid or pointing to a different virtual host. After TLS negotiation, the Host header only works once the connection is established, so Apache typically handles virtual host selection. Often, switching to plain HTTP between Nginx and Apache is a safer approach since it stays within your trusted network. If you prefer not to change this, adjusting Nginx to use a different hostname for SNI could help it request the correct domain.
S
SlayFuzzy
11-29-2025, 04:25 AM #2

The Nginx reverse proxy must decrypt the traffic, yet your snippet doesn<|pad|> to lack TLS setup. At least ensure Nginx uses the same certificates as Apache currently employs. Another issue could be that Nginx is redirecting from 192.168.0.146 instead of your intended domain, making the presented certificate invalid or pointing to a different virtual host. After TLS negotiation, the Host header only works once the connection is established, so Apache typically handles virtual host selection. Often, switching to plain HTTP between Nginx and Apache is a safer approach since it stays within your trusted network. If you prefer not to change this, adjusting Nginx to use a different hostname for SNI could help it request the correct domain.

Z
zlip88
Member
198
12-06-2025, 05:53 PM
#3
You're wondering about applying the same TLS certificate to Nginx. It's a common setup, just place the certificate file in the correct directory for your server configuration.
Z
zlip88
12-06-2025, 05:53 PM #3

You're wondering about applying the same TLS certificate to Nginx. It's a common setup, just place the certificate file in the correct directory for your server configuration.

O
Ob22007
Member
121
12-09-2025, 11:48 AM
#4
Within the server block, insert ssl_certificate /etc/letsencrypt/live/(my domain)/fullchain.pem and ssl_certificate_key /etc/letsencrypt/live/(my domain)/privkey.pem. Then restart nginx.
O
Ob22007
12-09-2025, 11:48 AM #4

Within the server block, insert ssl_certificate /etc/letsencrypt/live/(my domain)/fullchain.pem and ssl_certificate_key /etc/letsencrypt/live/(my domain)/privkey.pem. Then restart nginx.

B
Bliep2
Member
81
12-09-2025, 07:05 PM
#5
Wow, it actually helped!
B
Bliep2
12-09-2025, 07:05 PM #5

Wow, it actually helped!