Portforwarded FE not able to access API when connecting via WAN, fine on WAN #1867

Closed
opened 2026-03-22 13:42:59 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @jamess60 on GitHub (Jul 8, 2023).

Description

When connecting to my front end via lan with http://ip.ip.ip.ip:feport/, I am able to log in without issues.

If I use cloudflare tunnel to make my FE public (vikunja.subdomain.tld), I reach the FE web page, but it says it cant find the API. using http://ip.ip.ip.ip:3456/api/v1 does not work.

If I were to port forward the api port, could I then use vikunja.subdomain.tld:3456/api/v1 in my api location box?
If not, what is the recommended way to portforward vikunja for WAN access?

Note that cloduflare tunnel does https for me, I have new registrations disabled and 2fa enabled so this should be fairly safe

Vikunja Frontend Version

docker:latest

Vikunja API Version

docker:latest

Browser and version

Firefox Developer Edition 116.0b1 macOS

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @jamess60 on GitHub (Jul 8, 2023). ### Description When connecting to my front end via lan with http://ip.ip.ip.ip:feport/, I am able to log in without issues. If I use cloudflare tunnel to make my FE public (vikunja.subdomain.tld), I reach the FE web page, but it says it cant find the API. using http://ip.ip.ip.ip:3456/api/v1 does not work. If I were to port forward the api port, could I then use vikunja.subdomain.tld:3456/api/v1 in my api location box? If not, what is the recommended way to portforward vikunja for WAN access? Note that cloduflare tunnel does https for me, I have new registrations disabled and 2fa enabled so this should be fairly safe ### Vikunja Frontend Version docker:latest ### Vikunja API Version docker:latest ### Browser and version Firefox Developer Edition 116.0b1 macOS ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
Author
Owner

@jamess60 commented on GitHub (Jul 8, 2023):

Update - Managed to fix my own issue.
I was able to use the example in the full docker config guide to setup nginx as a proxy - https://vikunja.io/docs/full-docker-example/

CT tunnel now points to the nginx proxy, nginx handles the rest.

@jamess60 commented on GitHub (Jul 8, 2023): Update - Managed to fix my own issue. I was able to use the example in the full docker config guide to setup nginx as a proxy - https://vikunja.io/docs/full-docker-example/ CT tunnel now points to the nginx proxy, nginx handles the rest.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1867