Cannot access docker image behind pfsense haproxy

reymond070605 · June 24, 2024, 7:21pm

Hi, Everyone.

I have a problem where a server hosted in a docker cannot be accessed when behind pfsense haproxy. Please help me identify what configuration mistake I have done or a setting that I may have overlook.

I have setup a docker server and setup portainer, freshrss and joplin in it. All of those will only be accessed internally via haproxy. If I access them directly they are working fine:

Once I have place them behind the haproxy and access them by name it failed:

Below are my haproxy settings:

Joplin settings:

xMAXIMUSx · June 24, 2024, 10:41pm

Joplin has a GitHub issue for reverse proxies. I don’t know it right off the top of my head but I ran into this when I was setting up a Joplin server in docker.

EDIT:
The issue is closed but you will need to find a way to add what people are suggesting in the comments.

github.com/laurent22/joplin

Joplin Server fails on reverse proxy with "Invalid origin"

opened 03:17AM - 13 Aug 21 UTC

closed 02:50PM - 13 Jan 22 UTC

jansende

bug stale

I have successfully set up Joplin in a local docker container. I am now trying t…o pass it to my private domain using a reverse proxy, but it is not working. ## Environment Joplin version: 2.1.2 Platform: Linux NAS OS specifics: Docker ```yaml version: '3' services: db: image: postgres:13.1 volumes: - /local/path:/var/lib/postgresql/data restart: unless-stopped environment: - APP_PORT=22300 - POSTGRES_PASSWORD=******** - POSTGRES_USER=user - POSTGRES_DB=database app: image: joplin/server:2.1.2 depends_on: - db ports: - "22300:22300" restart: unless-stopped environment: - APP_PORT=22300 - APP_BASE_URL=http://192.168.1.2:22300/ - DB_CLIENT=pg - POSTGRES_PASSWORD=******** - POSTGRES_DATABASE=database - POSTGRES_USER=user - POSTGRES_PORT=5432 - POSTGRES_HOST=db ``` ## Steps to reproduce 1. I setup an nginx reverse proxy using the following configuration. ```nginx server { listen 80; listen [::]:80; server_name my.example.org; location / { proxy_pass http://192.168.1.2:22300; } } ``` 2. When trying to access Joplin via my.example.org, the connection fails with error 502: Bad Gateway 3. nginx provides the following message: ``` 2021/08/13 02:44:08 [error] 24#24: *4 upstream timed out (110: Connection timed out) while connecting to upstream, client: 123.45.67.89, server: my.example.org, request: "GET / HTTP/1.1", upstream: "http://192.168.1.2:22300/", host: "my.example.org" ``` 4. Joplin itself provides the following: ``` 2021-08-13 02:44:08: [error] App: 404: GET / : Invalid origin: http://127.0.0.1:22300 ``` When using the local http://192.168.1.2:22300/ instead, everything works fine. ## Describe what you expected to happen As the nginx configuration I am using works fine with my other services, I expect this to be an issue with the Joplin Server. Maybe, the forwarded messages are not handled properly?

reymond070605 · June 25, 2024, 11:55am

Hi, xMAXIMUSx.

Thanks for providing this link, as I read the article the configuration is very challenging. I will evaluate if I will have time to do it or not.

liquidjoe · June 25, 2024, 1:09pm

Sounds like you are treating HAProxy as a security service, like a VPN. This is arguably incorrect.

Also, keep in mind you are running a high profile and very exposed piece of code directly on your router. This is bad design. Instead of running this service on a separate device, tucked away in a isolated VLAN, you have it running naked on your router. I think Netgage should remove this from their repository.

reymond070605 · May 4, 2025, 9:48am

Apologies for the late reply, why did you say I am using HAProxy as a VPN? As mention in my initial post, I am using this to access Joplin internally and not exposed to the Internet.