-
Notifications
You must be signed in to change notification settings - Fork 14
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
DSMR configuration page not working through Ingress #95
Comments
Same issue here |
For me as well but only if I access Home Assistant through my ddns domain name via https. If I access Home Assistant via local ip then the DSMR configuration panel opens fine. |
I verified the problem. I will add it on my to do list after my holiday. For now indeed like @rboeters is saying, use the configuration panel from the internal ip address. |
Unfortunately that is not a workaround for me, I get the same error on the internal IP and outside URL |
I'm running into the same issue, unfortunately the workaround does not work for me either. |
Confirmed, will wait for the next DSMR Reader release. So for now you have to configure the software internally with a non secure address. |
Gives this error:
Verboden (403)
CSRF-verificatie mislukt. Aanvraag afgebroken.
U ziet deze melding, omdat deze HTTPS-website vereist dat uw webbrowser een ‘Referer header’ meestuurt, maar deze ontbreekt. Deze header is om veiligheidsredenen vereist om er zeker van te zijn dat uw browser niet door derden wordt gekaapt.
Als u ‘Referer’-headers in uw browser hebt uitgeschakeld, schakel deze dan weer in, op zijn minst voor deze website, of voor HTTPS-verbindingen, of voor ‘same-origin’-aanvragen.
Als u de tag gebruikt of de header ‘Referrer-Policy: no-referrer’ opneemt, verwijder deze dan. De CSRF-bescherming vereist de ‘Referer’-header voor strenge referer-controle. Als u bezorgd bent om privacy, gebruik dan alternatieven zoals <a rel="noreferrer" …> voor koppelingen naar websites van derden.
Meer informatie is beschikbaar met DEBUG=True.
Sorry for it being in dutch :-)
It's only the configuration page, were you need to login. After entering username password this error occurs. All other pages are working normal.
The text was updated successfully, but these errors were encountered: