Replies: 1 comment
-
Similar or same issue issue for me. (latest version @ 25 Jan 2025). I have set Blinko up behind nginx proxy manager, like I have for many others. Mapping port 1111 to my host directly in docker allows me direct access to Blinko at blinko-website is definitely in my nginx docker network, I've verified that. I've tried commenting out the two env variables listed in the OP, and numerous other things, but no luck. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I have set Nextauth and public set to my domain behind nginx proxy manager, but it seems like it can't reach it.
I have set as follows
NEXTAUTH_URL: https://blinko.example.com
NEXT_PUBLIC: https://blinko.example.com
BTW: Since your last update, the username and password default is render useless as your able to
sign up for the initial account. You may want to remove that from the main page so that it doesn't cause confusion.
When I get the container up and running and then trying to access via blinko.example.com, I just get a 502 error as if it can't be reached
Beta Was this translation helpful? Give feedback.
All reactions