-
Notifications
You must be signed in to change notification settings - Fork 65
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
[BUG] cloudflared proxied faikin not working #411
Comments
Sounds like something is adding (long) header fields? |
I dont really know, never had problem on any apps with those tunnels witch acts like a proxy over vpn |
Well it is a tiny microcontroller and allocates some static buffers in the http server handling. So the config needs to know how big. It would help to know what headers and how big! |
Ixhave non Idea how to proceed but if you need some logs i Can have a try |
I don't know either, the http server is part of the ESP IDF, so not sure if I can get any logs, and if I could it would be over a serial debug port. Do you have anything else you can access in the same way that allows you to dump/report what headers are sent? Or can you packet dump on your LAN (this is http not https so should be clear). |
If you are able to find headers being sent, but setting something else to access by proxy, then that may allow me to address the issue. Re-open if/when you do. |
Faikin hardware
Faikin-S3-MINI-N4-R2:
Daikin hardware
S21
Describe the bug
im getting access to my homelab using cloudflared tunnelling but impossible to get access to faikin interface.
On local LAN works without problems, but after proxying it through cloudflared got following errors : "Header fields are too long"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
nomal access to the page.
Additional context
all my homelab apps are proxied using cloudflare without any problem
The text was updated successfully, but these errors were encountered: