mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #752] How to use wordpress docker(5.5.3-php7.2-fpm-alpine) with nginx proxy manager #637
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#637
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @quangnv1311 on GitHub (Dec 2, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/752
I will setup a wordpress web with docker use the wordpress:php-fpm-alpine image. I already know how to configure nginx to set it up to work. But now I like the nginx proxy manager because of its features. But I don't know how wordpress fpm alpine works with nginx proxy manager. Can someone help me config nginx-proxy-manager?
@osnet commented on GitHub (Dec 3, 2020):
easy peasy:
wordpress docker on host X with exposed port 1234
nginx manager thes just need to point the new subdomain to X:1234
just like normal operation with manual edited configs , here only with gui frontend
@dokbua commented on GitHub (Dec 6, 2020):
I don't know if it's that easy peasy :)
I already have a working NPM container configured and working with the default wordpress container, going to http://wpdemo1_wordpress_1:80 through an external nginx-proxy network.
This works fine, but of course has the overhead of the apache webserver, so I'm trying to get this to work with wordpress:fpm.
So what you say is, just replace the wordpress image with wordpress:fpm, and point NPM to port 9000 instead? I'm getting a 502 bad gateway with that? Any ideas?
@osnet commented on GitHub (Dec 6, 2020):
aaaah
now the situation is more clear
sounds like you are willing to „abuse“ npm as webserver ??
idk if that is useful
if u dont want apache-fpm build your own wordpress image with nginx-fpm?
rcd notifications@github.com schrieb am So. 6. Dez. 2020 um 02:38:
@dokbua commented on GitHub (Dec 6, 2020):
My bad, I obviously misunderstood the interactions between NPM and FPM. Thanks anyway!
@igormages commented on GitHub (Mar 15, 2021):
Thats exactly what i'm trying to do. Someone has a solution ?
@chaptergy commented on GitHub (May 12, 2021):
That is not possible. For progress on this see https://github.com/jc21/nginx-proxy-manager/issues/58, though someone from the community would have to develop this and make a PR.
@geekyayush commented on GitHub (Aug 6, 2023):
Is there any way we could do this?
Sorry for commenting on this old issue, but I really need to use "fastcgi_pass" for my Wordpress site using php-fpm.
Normal Wordpress setup without php-fpm and with just PHP works fine. But when I use Wordpress php-fpm version, I get 502 error when visiting my domain.
I would really appreciate if someone could tell me a way to use "fastcgi_pass" instead of proxy_pass