starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #980] 502 Bad Gateway only for Apache on Ubuntu Server 20.04 #824

New issue

Closed

opened 2026-02-26 06:34:34 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:34:34 +03:00

Owner

Originally created by @doofit on GitHub (Mar 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/980

Hello,

I am running nginx proxy manager (latest) on a machine in docker and everything works fine for all my containers & services, except for one: Apache webserver running on Ubuntu Server 20.04 on a virtual machine.

I do get a 502 Bad Gateway error in my browser when trying to visit a page on the server via a domain CNAME.
I can successfully access the server from inside my local network via the IP address.
I have various other services running on different machines and docker containers, all working 100% via domain CNAME. So via DuckDNS the request comes into nginx proxy manager (just as it does for all other subdomains/CNAMEs + services), but then gets the 502 error.

It seems like this only affects the Apache server (clean installation, no messing around with configs etc.) - I tried setting up a virtual host on another port, but it's the same result. Internally, I can access everything. Externally, I get a 502 Bad Gateway.

Any idea what I am missing? It seems weird that it only affects this one service.

Thanks for any hint that might resolve the issue.

Originally created by @doofit on GitHub (Mar 28, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/980 Hello, I am running nginx proxy manager (latest) on a machine in docker and everything works fine for all my containers & services, except for one: Apache webserver running on Ubuntu Server 20.04 on a virtual machine. I do get a 502 Bad Gateway error in my browser when trying to visit a page on the server via a domain CNAME. I can successfully access the server from inside my local network via the IP address. I have various other services running on different machines and docker containers, all working 100% via domain CNAME. So via DuckDNS the request comes into nginx proxy manager (just as it does for all other subdomains/CNAMEs + services), but then gets the 502 error. It seems like this only affects the Apache server (clean installation, no messing around with configs etc.) - I tried setting up a virtual host on another port, but it's the same result. Internally, I can access everything. Externally, I get a 502 Bad Gateway. Any idea what I am missing? It seems weird that it only affects this one service. Thanks for any hint that might resolve the issue.

kerem

2026-02-26 06:34:34 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:34:35 +03:00

Author

Owner

@traderpedroso commented on GitHub (Apr 6, 2021):

me too was working b4 i have new server and setup with last Version and not working too return 502 bad Gateway

@traderpedroso commented on GitHub (Apr 6, 2021): me too was working b4 i have new server and setup with last Version and not working too return 502 bad Gateway

kerem commented

2026-02-26 06:34:35 +03:00

Author

Owner

@Brendonwbrown commented on GitHub (Apr 8, 2021):

I've got the same configuration: Apache on Ubuntu VM. Worked for me when I set up a month ago, now it's giving me 502s.

@Brendonwbrown commented on GitHub (Apr 8, 2021): I've got the same configuration: Apache on Ubuntu VM. Worked for me when I set up a month ago, now it's giving me 502s.

kerem commented

2026-02-26 06:34:35 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 15, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 15, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:34:35 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 27, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 27, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#824

No description provided.

Rows
Columns