Login API route causes weirdness in web instance (solved)
Has anyone had an issue where self-hosted works fine on http, but switching to https causes the api to log stuff such as this:
I'm behind a traefik reverse proxy.
This results in a 431 Request Header Fields Too Large when attempting to log in from the web view.
I'm on v 24.1
Solution:
Use subdomains rather than paths for each services
4 Replies
Hi @Dauntless, I'm an AI assistant for Novu. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Hmm.. Seems there was an issue processing this question. Please try again or tag a team member.
@Dima Grossman Could you have a look at this?
Hi @Dauntless unfortuently I haven't encountered this behavioud before 😦
How are you running your HTTPS setup?
VPS on Hetzner through Coolify. I have a modified docker-compose and my own env vars
Would you like to see?
Btw, do you know the proxy url is hard coded here?
From apps/web/package.json
`
If I change from https to http, it works fine, but I get cors error mixed-content on my frontend (Where I'm integrating Novu)
Now I'm exposing this to both http and https domains at the same time, and the http urls work, but the https ones causes weird behaviour
Let me know what more you need @Dima Grossman
I managed to getting running by changing from novu.domain.com/path subdomains like api.novu.domain.com