ProxyError at login #383

Status quo

Sometimes the following error is thrown:

ProxyError at /login/
HTTPSConnectionPool(host='login.naturschutz.rlp.de', port=443): Max retries exceeded with url: /sso/request-token/ (Caused by ProxyError('Unable to connect to proxy', RemoteDisconnected('Remote end closed connection without response')))

...

  File "/usr/local/lib/python3.11/site-packages/requests/adapters.py", line 513, in send
    raise ProxyError(e, request=request)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Exception Type: ProxyError at /login/
Exception Value: HTTPSConnectionPool(host='login.naturschutz.rlp.de', port=443): Max retries exceeded with url: /sso/request-token/ (Caused by ProxyError('Unable to connect to proxy', RemoteDisconnected('Remote end closed connection without response'))) Raised during: simple_sso.sso_client.client.LoginView

The error is resolved by itself after a very short period of time (few seconds).

This needs further investigation.

# Status quo Sometimes the following error is thrown: ```python ProxyError at /login/ HTTPSConnectionPool(host='login.naturschutz.rlp.de', port=443): Max retries exceeded with url: /sso/request-token/ (Caused by ProxyError('Unable to connect to proxy', RemoteDisconnected('Remote end closed connection without response'))) ... File "/usr/local/lib/python3.11/site-packages/requests/adapters.py", line 513, in send raise ProxyError(e, request=request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Exception Type: ProxyError at /login/ Exception Value: HTTPSConnectionPool(host='login.naturschutz.rlp.de', port=443): Max retries exceeded with url: /sso/request-token/ (Caused by ProxyError('Unable to connect to proxy', RemoteDisconnected('Remote end closed connection without response'))) Raised during: simple_sso.sso_client.client.LoginView ``` The error is resolved by itself after a very short period of time (few seconds). This needs further investigation.

ssl_error.png

47 KiB

Further research led to the gunicorn configuration of arnova. It looks like only one worker process dealed with all the incoming requests. The configuration has been edited, so that arnova is running with 4 workers now. I will keep an eye on this.

Further research led to the gunicorn configuration of `arnova`. It looks like only one worker process dealed with all the incoming requests. The configuration has been edited, so that `arnova` is running with 4 workers now. I will keep an eye on this.

Might become irrelevant due to switch to OAuth2.0 workflow (See #396 and #395)

Labels Milestones

ProxyError at login #383

Status quo