# Docker Nginx Proxy Manager

**URL:** <https://community.vikunja.io/t/docker-nginx-proxy-manager/3402>\
**Category:** Support\
**Created:** [15 February 2025 21:13 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402 "2025-02-15T21:13:52Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcel86](https://community.vikunja.io/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@Marcel86](https://community.vikunja.io/u/Marcel86)\
**Post date:** [15 February 2025 21:13 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/1 "2025-02-15T21:13:53Z")

</div>

Hello everyone,

Now that I can access Vikunja locally via  
[http://192.168.178.20:3456/](http://192.168.178.20:3456/) and was able to create an account there, I would like to take the next step and make Vikunja accessible from outside via Nginx Proxy Manager.  
I already have:

- One domain: vikunja.stratoDomain.eu
- For this domain I remove the DNS rebind protection in my fritz.box
- I have gone through the settings for the Nginx Proxy Manager as described here: [Setup behind a reverse proxy](https://vikunja.io/docs/reverse-proxy/#in-nginx-proxy-manager) It looks like this for me:  
(_But I have to admit that the DNS Challange is active in the background. There is no other way to generate a certificate._)

> **Nginx Proxy Manager settings**
>
> ![image](https://community.vikunja.io/uploads/default/original/2X/4/47702c547373fcf77fed39caca2e37823be13843.png)  
> ![image](https://community.vikunja.io/uploads/default/original/2X/d/d95073a98916bf75e1c21020dd2b666277cda683.png)  
> ![image](https://community.vikunja.io/uploads/default/original/2X/b/bfcb34e890423b0ee103678ab4f78fcdb77e6c4a.png)  
> ![image](https://community.vikunja.io/uploads/default/original/2X/c/ca1025755642a2ad4ee37a0f91277b2f62b47e09.png)

- I have adapted the Docker compose file as follows and then run it as a stack in portainer:

> **Portainer Stack**
>
> services:  
> vikunja:  
> image: vikunja/vikunja  
> environment:  
> VIKUNJA\_SERVICE\_PUBLICURL: [https://vikunja.stratoDomain.eu/](https://vikunja.stratoDomain.eu/) # [http://192.168.178.20](http://192.168.178.20)  
> VIKUNJA\_DATABASE\_HOST: db  
> VIKUNJA\_DATABASE\_PASSWORD: test  
> VIKUNJA\_DATABASE\_TYPE: mysql  
> VIKUNJA\_DATABASE\_USER: vikunja  
> VIKUNJA\_DATABASE\_DATABASE: vikunja  
> VIKUNJA\_SERVICE\_JWTSECRET: test  
> ports:  
> - 3456:3456  
> volumes:  
> - /volume1/docker/vikunja/files:/app/vikunja/files  
> depends\_on:  
> db:  
> condition: service\_healthy  
> restart: unless-stopped
> 
> db:  
> image: mariadb:10  
> command: --character-set-server=utf8mb4 --collation-server=utf8mb4\_unicode\_ci  
> environment:  
> MYSQL\_ROOT\_PASSWORD: test  
> MYSQL\_USER: vikunja  
> MYSQL\_PASSWORD: test  
> MYSQL\_DATABASE: vikunja  
> volumes:  
> - /volume1/docker/vikunja/db:/var/lib/mysql  
> restart: unless-stopped  
> healthcheck:  
> test: [“CMD-SHELL”, “mysqladmin ping -h localhost -u $$MYSQL\_USER --password=$$MYSQL\_PASSWORD”]  
> interval: 2s  
> start\_period: 30s

With these settings, Vikunja cannot be accessed via [https://vikunja.stratoDomain.eu](https://vikunja.stratoDomain.eu):MyForwardedHTTPSPort  
Does anyone have any ideas what else I could try?

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [15 February 2025 21:43 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/2 "2025-02-15T21:43:23Z")

</div>

Can you verify that your DNS is working correctly?

---

<div class="post-metadata">

**Author:** ![Marcel86](https://community.vikunja.io/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@Marcel86](https://community.vikunja.io/u/Marcel86)\
**Post date:** [16 February 2025 11:30 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/3 "2025-02-16T11:30:09Z")

</div>

OMG!  
Many thanks for this pointer!!

I used [Online Ping, Traceroute, DNS lookup, WHOIS, Port check, Reverse lookup, Proxy checker, Bandwidth meter, Network calculator, Network mask calculator, Country by IP, Unit converter](https://ping.eu/nslookup/) to figure out that Strato “forgott” my Subdomain settings (cname).

Now I reach  
[https://vikunja.stratoDomain.eu](https://vikunja.stratoDomain.eu):MyOpenHTTPSPort

But I’m stuck in an loop ☹

 ![grafik](https://community.vikunja.io/uploads/default/original/2X/b/b34eeb4f9ceae4c77b599f936e1c70a86b89f2e2.png)

Adding /api/v1 shows me:

{“message”:“missing, malformed, expired or otherwise invalid token provided”}

Any idea what is meant with invalid token?

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [16 February 2025 19:37 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/4 "2025-02-16T19:37:18Z")

</div>

> [@Marcel86](#):
>
> But I’m stuck in an loop ☹

Is there anything in the dev tools?

> [@Marcel86](#):
>
> Adding /api/v1 shows me:
> 
> {“message”:“missing, malformed, expired or otherwise invalid token provided”}
> 
> Any idea what is meant with invalid token?

That’s expected. The response comes from the api, that means you can reach it.

You’d need to pass a token as the `Authorization` header, which browsers don’t do unless you write code to do it.

---

<div class="post-metadata">

**Author:** ![Marcel86](https://community.vikunja.io/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@Marcel86](https://community.vikunja.io/u/Marcel86)\
**Post date:** [16 February 2025 20:08 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/5 "2025-02-16T20:08:33Z")

</div>

Hi

> Is there anything in the dev tools?

I don’t understand that ☹ . Which develepment tools do you mean? What can I check and how? Do you have a link for me?  
Do you mean the Development Section from the Vikunja Docs? Do you have a specific section in mind that I should check?

> pass a token as the `Authorization` header

Do you have any instructions on how to do this?  
And why is the behavior here different from when I access Vikunja locally via 192.168.x.x.:3456? I can access the login screen locally and can also log in after creating an account. Is there a technical reason for this?

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [16 February 2025 20:29 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/6 "2025-02-16T20:29:54Z")

</div>

> [@Marcel86](#):
>
> I don’t understand that ☹ . Which develepment tools do you mean? What can I check and how? Do you have a link for me?  
> Do you mean the Development Section from the Vikunja Docs? Do you have a specific section in mind that I should check?

The dev tools are actually built into your browser - no need to install anything. You can open them by:

- In Chrome/Edge: Press F12 or right-click anywhere on the page and select “Inspect”
- In Firefox: Press F12 or right-click and select “Inspect Element”

There should be a tab called “Console”. With that tab open, reload the page where you see the loading spinner. If there is something wrong, it should show up there.

> [@Marcel86](#):
>
> Do you have any instructions on how to do this?  
> And why is the behavior here different from when I access Vikunja locally via 192.168.x.x.:3456? I can access the login screen locally and can also log in after creating an account. Is there a technical reason for this?

The error with the Authorization header is something that Vikunja uses when you use Vikunja normally through its interface. You only see this error because you’re trying to access the API directly in your browser. You only need to use this directly when you’re programming tools to interact with Vikunja’s API directly.

The reason it works when you access it via 192.168.x.x:3456 is because you’re accessing the full Vikunja application there, which handles all the login stuff for you behind the scenes. When you try to access the API directly (`/api/v1`), you’re bypassing all of that, which is why you get the error.

---

<div class="post-metadata">

**Author:** ![Marcel86](https://community.vikunja.io/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@Marcel86](https://community.vikunja.io/u/Marcel86)\
**Post date:** [16 February 2025 21:02 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/7 "2025-02-16T21:02:50Z")

</div>

Ah 💡

I wrote above that I am trapped in a loop.  
I have just realized that this is apparently not quite right.

After a very, very long time, I end up at  
[https://vikunja.stratoDomain.eu](https://vikunja.stratoDomain.eu):myOpenHTTPSPort  
at this point:

> **Screenshots**
>
> ![grafik](https://community.vikunja.io/uploads/default/original/2X/a/a498528e46c6a38f8228587e47cc8de00366fe9b.jpeg)  
> after being stuck here for a long time:  
> ![grafik](https://community.vikunja.io/uploads/default/original/2X/2/2279040fe5b02c21c40cc5f7c75899d30721d72a.png)

I don’t want to call the API at all, I only tried it because I read something like that here in the forum and I hoped to get more information about it.

hm… probably the error is here (from the DEV section of the browser):

Cross-source (cross-origin) request blocked: The same-source rule prohibits reading the external resource at [https://vikunja](https://vikunja). **stratoDomain**.eu/api/v1/info. (Reason: CORS request failed). Status code: (null).  
and

Cross-source (cross-origin) request blocked: The same-source rule prohibits reading the external resource on [https://vikunja](https://vikunja). **stratoDomain**.eu: **3456** /api/v1/info. (Reason: CORS request failed). Status code: (null).

I don’t understand this yet and need to read in. Help is welcome 🙂 See also the following comment.  
But what I am also wondering here: Why a mix between external domain and internal port occurs here. This should actually be managed by NGINX Proxy Manager. But maybe that doesn’t matter.

What makes me wonder is that I have set up my https access to immich and vaultwarden in an almost identical way, which also works.

> because you’re accessing the full Vikunja application there

Thank you for the explanation

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [17 February 2025 16:11 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/8 "2025-02-17T16:11:11Z")

</div>

> [@Marcel86](#):
>
> But what I am also wondering here: Why a mix between external domain and internal port occurs here. This should actually be managed by NGINX Proxy Manager. But maybe that doesn’t matter.

Does your [publicurl](https://vikunja.io/docs/config-options/#1-service-publicurl) contain the port?

---

<div class="post-metadata">

**Author:** ![Marcel86](https://community.vikunja.io/letter_avatar_proxy/v4/letter/m/5f9b8f/32.png) [@Marcel86](https://community.vikunja.io/u/Marcel86)\
**Post date:** [17 February 2025 18:07 UTC](https://community.vikunja.io/t/docker-nginx-proxy-manager/3402/9 "2025-02-17T18:07:28Z")

</div>

OMG ²

That was it - I needed to change it to  
[https://vikunja.startoDomain.eu](https://vikunja.startoDomain.eu):MyOpenHTTPSPort

I read (I think) somewhere that publicurl should be without Port. Therefore I didn’t try this before :-/

Thank you verry much!
