Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reverse proxy #76

Closed
firestrife23 opened this issue Nov 13, 2024 · 7 comments
Closed

Reverse proxy #76

firestrife23 opened this issue Nov 13, 2024 · 7 comments

Comments

@firestrife23
Copy link

I enjoy it, but for some reason it didn't function with Traefik, which manages SSL termination. I also tried setting the environment for the public-facing URL, and it's still not working for me.

@blinko-space blinko-space added the bug Something isn't working label Nov 13, 2024
@tzwaeaen
Copy link

For me the healthcheck was not working. I removed it from the docker compose and now it is working with traefik. 🤷

@blinko-space blinko-space removed the bug Something isn't working label Nov 27, 2024
@blinko-space
Copy link
Owner

this might not be an issue with Blinko. I would suggest checking your Traefik configuration to ensure there are no routing or SSL termination issues. Make sure Traefik is correctly handling the HTTPS requests and that the relevant environment variables are set properly."

@victornavorskie
Copy link

Same problem here, with NEXTAUTH_URL showing Bad Gateway.

@majoragee
Copy link

majoragee commented Jan 7, 2025

I believe this may be a bug. Blinko is binding to the first docker network and is unreachable from other networks. In my environment, traefik runs on the webproxy network and blinko and postgres also share the backend network, which docker compose creates as blinko-backend-1. Because blinko-backend-1 was alphabetically before webproxy, blinko was binding to blinko-backend-1 and was unreachable from webproxy. I was able to work around the issue by defining my networks as follows:

networks:
  webproxy:
    external: true
  backend:
    name: zzz-blinko-backend

@jermanoid
Copy link

That worked for me. I was on that path initially and tried ordering them in compose which didn't change the subnet listed in the blinko logs at runtime. Glad I stumbled on this

@ChickenSaysBak
Copy link

ChickenSaysBak commented Jan 26, 2025

I also experienced this using Caddy.

Setting blinko's network name to "z-blinko-network" did the trick. Thanks!

@akrauss
Copy link

akrauss commented Feb 8, 2025

Why closed, this is a Bug!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants