After Upgrade to 5.13 HTTP/HTTPS Farms not working anymore.

[Trylok]

After starting a HTTP farm the farms list ist empty.

l4xnat farms are working but not displayed anymore. Only stopping the corresponding Virtual Interface and rebooting the system brings the List back. For testing i did a fresh iso install, only creating a new HTTP farm. With the same result.

HTTP/HTTPS Farms do not work anymore, no matter on upgrade or fresh install.

Thanks, Michael

[ct-utel]

It looks like TeamCity might but should be able to fallback if unavailable and Home Assistant can for API calls but not the GUI itself.

[emiliocampos-zevenet]

Thanks for the confirmation, I guess we have to take this information into consideration in order to investigate further in this issue.

Regards!

El lun, 20 mar 2023 a las 14:40, ct-utel @.***>) escribió:

It looks like TeamCity might but should be able to fallback if unavailable and Home Assistant can for API calls but not the GUI itself.

[image: image] https://user-images.githubusercontent.com/127128354/226357110-c6cad877-6df8-4425-8306-b7bb26bf44ef.png

— Reply to this email directly, view it on GitHub https://github.com/zevenet/zlb/issues/123#issuecomment-1476255172, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBQEPFZPQX7U6XH3YUHUVLW5BM4FANCNFSM6AAAAAAVKR3R5Y . You are receiving this because you commented.Message ID: @.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com

Review ZEVENET Product at Gartner Insights https://gtnr.io/LfXtqnsSr https://www.linkedin.com/company/zevenet https://twitter.com/zevenet https://www.facebook.com/zevenet https://github.com/zevenet [image: ZEVENET] https://www.zevenet.com/signature/

DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[Kroki0815]

Hi, i also run in this situation ( timeout for request ...) and i figured out that only pages are not working which are using chunked transfers. I have now removed the Request-Header 'Accept-Encoding' in the Farm-Configuration and all is working like before.

Kroki

[nevola]

Hi @Trylok could you please increase Client timeout from 30 to 60, and see if there is any improvement?

Thank you.

[Trylok]

@nevola Makes no difference on the https farms. On l4xnat farms there is no timeout option anyway. And they don't work properly either. Problems described above. No problems what so ever on the previous versions (<=5.12.2) with the same settings on all farms.

[nevola]

Hi @Trylok , Good news.

We have a new binary with several fixes that might resolve your issues. Please download it from here:

https://drive.google.com/file/d/1s9iA28TsD07kcvr5OSIiHW5l8J562KsV/view?usp=share_link

You've to upload to the appliance and rename it in the path /usr/local/zevenet/app/zproxy/bin/zproxy (Please rename the current one in case of rollback)

After that, please restart the farms and let us know how it goes, Thank you!

[Kroki0815]

Hi, i also run in this situation ( timeout for request ...) and i figured out that only pages are not working which are using chunked transfers. I have now removed the Request-Header 'Accept-Encoding' in the Farm-Configuration and all is working like before.

Kroki

With the new Binary i didn't see any issues with chunked transfers any more.

Kroki

[nevola]

@Kroki0815 thank you for the confirmation.

[Trylok]

@nevola Made it worse. With the new zproxy http farms not starting anymore (error in configfile), If you try to create a new one, error message says "cannot save farm"

[Trylok]

@nevola Sorry, forgot to make the file executable. So far it looks like its working now. I have to test it further.

[Trylok]

@nevola After further testing i had to rollback. On https farm with ssl backends i have credentials errors (401) and pending connections. Here a supportsave from this situation. supportsave_ZEVENET_20230330_2303.tar.gz

[naortega]

On https farm with ssl backends i have credentials errors (401) and pending connections.

We'll have a look into the authorization errors (401 response code). The pending connections seems to be an issue with the counter, but it should not be an issue with actual connections pending. We'll try resolving these issues as soon as possible.

[naortega]

@Trylok Would it be possible for you to send a HAR that displays the 401 error you get? Is it when connecting via websocket? Is it a normal HTTP POST request?

[Trylok]

@naortega I have to wait until evening to test it. But it is an HTTP POST request.

[nevola]

Hi @Trylok could you please enable farm logs, then reproduce the problem and then generate a new support save to support@zevenet.com (please do not send it via github). Thank you!

[Trylok]

File has been send.

[naortega]

@Trylok In the most recent release of Zproxy (0.9.4) we've resolved the issue of pending connections counting. Are you still having these issues? Also, in regards to the 401 responses, have these been resolved?

[Trylok]

@naortega No improvement with 9.4. Same credentials errors (401) and pending connections on https farms. Rolled back again. In the moment i have only a short time window for testing. Sorry i can not help you any further.

[naortega]

@naortega No improvement with 9.4. Same credentials errors (401) and pending connections on https farms. Rolled back again. In the moment i have only a short time window for testing. Sorry i can not help you any further.

Understood. Would you mind taking a look at the logs corresponding to these requests on the backends? Zproxy itself does not give 401 responses unless received from the backend. It may be possible that Zproxy is erroneously manipulating the requests such that your backend gives that response, in which case there should be some error log from your backend.