# Very difficult to set reverse proxy in Apache

**URL:** <https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150>\
**Category:** Support\
**Created:** [22 June 2022 02:26 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150 "2022-06-22T02:26:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shouqiang](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/shouqiang/32/14116_2.png) [@shouqiang](https://discourse.joplinapp.org/u/shouqiang)\
**Post date:** [22 June 2022 02:26 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150/1 "2022-06-22T02:26:09Z")

</div>

It's very difficult to set reverse proxy in Apache. Very bad experience. Cannot find any workable example for reference.

---

<div class="post-metadata">

**Author:** ![shouqiang](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/shouqiang/32/14116_2.png) [@shouqiang](https://discourse.joplinapp.org/u/shouqiang)\
**Post date:** [23 June 2022 03:54 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150/2 "2022-06-23T03:54:04Z")

</div>

If you are using docker (deploying the Joplin server and PostgreSQL) on the Apache server, the following reverse proxy conf MAY be helpful for you.

#PROXY-START/  
  
ProxyRequests Off  
SSLProxyEngine on  
ProxyPreserveHost On\*\*  
ProxyPass "/joplin" [http://172.17.0.2:22300](http://172.17.0.2:22300) # (IP address of container and port number)  
ProxyPassReverse "/joplin" [http://172.17.0.2:22300](http://172.17.0.2:22300) # (IP address of container and port number)  
  
#PROXY-END/

.env file looks like this:

APP\_BASE\_URL=[https://xxxx.com/joplin](https://xxxx.com/joplin) (PORT number is NOT necessary)  
APP\_PORT=22300

# 

DB\_CLIENT=pg  
POSTGRES\_PASSWORD=xxxx  
POSTGRES\_DATABASE=joplin  
POSTGRES\_USER=root  
POSTGRES\_PORT=5432  
POSTGRES\_HOST=172.17.0.3 (IP address of the container)

---

<div class="post-metadata">

**Author:** ![MrKanister](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/mrkanister/32/20054_2.png) [@MrKanister](https://discourse.joplinapp.org/u/MrKanister)\
**Post date:** [27 June 2022 14:23 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150/3 "2022-06-27T14:23:38Z")

</div>

For reverse proxying with apache, one can follow this guide (even though it is for Raspberry Pis)

> [@Guide for Joplin-Server on Raspberry Pi](https://discourse.joplinapp.org/t/guide-for-joplin-server-on-raspberry-pi/14702):
>
> Hi, this is an extensive guide on how to host your own Joplin server on a Raspberry Pi. I had a setup like this running on a Pi 4 and a Pi 5. Technically it would also work on Pi 3 models which support 64-bit operating systems. If you spot any mistakes, please reply to me! The guide was updated on 11.06.2025. 1 Dynamic DNS If you don't get a static IP address from your ISP, you will need a Dynamic DNS service. This sets a hostname which will be redirected to your IP. There are a lot of pro…

---

<div class="post-metadata">

**Author:** ![shouqiang](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/shouqiang/32/14116_2.png) [@shouqiang](https://discourse.joplinapp.org/u/shouqiang)\
**Post date:** [28 June 2022 11:54 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150/4 "2022-06-28T11:54:58Z")

</div>

Thank you, buddy.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/1/c/1c948e33314e232a0927789508474d8624f4270b.png) [@system](https://discourse.joplinapp.org/u/system)\
**Post date:** [28 July 2022 11:55 UTC](https://discourse.joplinapp.org/t/very-difficult-to-set-reverse-proxy-in-apache/26150/5 "2022-07-28T11:55:12Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.