# Request help: Joplin server cannot function properly through reverse proxy

**URL:** <https://discourse.joplinapp.org/t/request-help-joplin-server-cannot-function-properly-through-reverse-proxy/19189>\
**Category:** Support\
**Created:** [2 August 2021 00:09 UTC](https://discourse.joplinapp.org/t/request-help-joplin-server-cannot-function-properly-through-reverse-proxy/19189 "2021-08-02T00:09:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![JackGruber](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/jackgruber/32/3231_2.png) [@JackGruber](https://discourse.joplinapp.org/u/JackGruber)\
**Post date:** [2 August 2021 08:12 UTC](https://discourse.joplinapp.org/t/request-help-joplin-server-cannot-function-properly-through-reverse-proxy/19189/3 "2021-08-02T08:12:56Z")

</div>

- The APP\_BASE\_URL is wrong  
in your example it should be `APP_BASE_URL=http://10.0.0.2:7002`
- You need to set the headers for the origin check
- Redirection everything to `/login` would not work! You need also to redirect all other paths ...  
For example, requests to `http://10.0.0.2:7002/images/Logo.png` will end in `http://10.0.0.2:7002/login/images/Logo.png`

Search the forum for working configs, like for example:

> [@New Install - Invalid origin error](https://discourse.joplinapp.org/t/new-install-invalid-origin-error/17891/10):
>
> In case anyone is interested this is an nginx "sites-available" reverse-proxy file that uses self-signed certs, diverts port 80 to 443, adds a bit of hardening and also logging. It does work with 2.0.6-beta. { listen 80; server\_name joplin.example.lol; return 301 https://joplin.example.lol$request\_uri; } server { listen 443 ssl http2; server\_name joplin.example.lol; proxy\_read\_timeout 720s; proxy\_connect\_timeout 720s; proxy\_send\_timeout 720s; client\_max\_…

---

_[View the full topic](https://discourse.joplinapp.org/t/request-help-joplin-server-cannot-function-properly-through-reverse-proxy/19189)._