-
Notifications
You must be signed in to change notification settings - Fork 638
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
espurna behind apache reverse proxy #1825
Comments
this works for me
You might also have to set |
i had some problems with 1.13.5 can this be fixed with some setting in apache configuration ? |
Wait... You want to workaround lwip MTU related bug by putting reverse proxy between espurna and the client? |
just went back to my old 1.13.1 and it worked. i didn't tested with ab build like #1610. sry for that |
my general setup is apache reverse proxy <- openvpn -> haproxy -> servers/clients/IoT so it could somehow possibly to have quick workoround in that setup, not to set up an reverse proxy to fix the mtu issue |
#1610 (comment) paths are for PIO, but you can do the same with IDE installation. You just need to find where Cores 2.5.0 >= do use lwip2 by default already (still a selectable option), but you will see a pretty significant firmware size increase |
BTW, since the problem with packet size, check out the #1843 I would say it is in draft status, but it works for me on a temperature sensor + energy monitor board config without any problems so far. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
i'm running my espurna devices behind apache reverse proxy / haproxy setup.
could somebody give me an advice how the apache reverse proxy configuration has to be ?
or could migrate the example from
#937 (comment)
to an apache config ?
at the moment i have:
ProxyPass / http://10.100.10.62:80/
ProxyPassReverse / http://10.100.10.62:80/
ProxyPreserveHost On
ProxyRequests Off
RewriteEngine on
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule .* ws://10.100.10.1:6868%{REQUEST_URI} [P]
ServerName pump-brunnen.xxx.xx
thanks in advance
The text was updated successfully, but these errors were encountered: