cancel
Showing results for 
Search instead for 
Did you mean: 

Nuxeo Drive 4.x client tries to switch to https access which is not available

promanov_
Star Contributor
Star Contributor

My nuxeo server is behind a reverse proxy and is accessed by http. When configuring the client to connect with http it works perfectly and uses http url.

But after restart the nuxeo drive client switches automatically to https: 2019-10-23 14:59:25 21200 5124 INFO nxdrive.engine.engine Updated server url to https://SERVER.eu.ngrok.io/nuxeo

The proxy server returns HTTP 404 code, the https access doesn't exists. Here is the client log message: 2019-10-23 14:59:33 21200 17720 INFO nxdrive.manager Status code for https://SERVER.eu.ngrok.io/nuxeo/drive_browser_login.jsp = 404

But the client keeps calling with https ang getting error: 2019-10-23 15:00:02 21200 18156 DEBUG nuxeo.client Calling 'https://SERVER.eu.ngrok.io/nuxeo/site/automation/NuxeoDrive.GetChangeSummary' 2019-10-23 15:00:03 21200 18156 WARNING nxdrive.engine.watcher.remote_watcher Network error:

It seems that the client misinterpretes the test call on https support, which in this case is not an ssl error, and switches to https instead of keeping http.

Also it's quite surprising and misleading to have a behavior change on the first client connection and after its' restart.

Could you have a look on this please?

Versions: Server - 10.10 HF11 Nuxeo Drive client 4.2.0

1 ACCEPTED ANSWER

Mickaël_Schoent
Star Contributor
Star Contributor

The code that checks for SSL support is catching all errors, not just SSL ones. In your case, why the reverse proxy handles HTTPS (or seem to handle)? I think the proxy translates HTTPS traffic to HTTP and thus request errors, right?

FI the SSL check has been added with https://jira.nuxeo.com/browse/NXDRIVE-1647.

View answer in original post

9 REPLIES 9

promanov_
Star Contributor
Star Contributor

more logs when first connecting the account

Mickaël_Schoent
Star Contributor
Star Contributor

The code that checks for SSL support is catching all errors, not just SSL ones. In your case, why the reverse proxy handles HTTPS (or seem to handle)? I think the proxy translates HTTPS traffic to HTTP and thus request errors, right?

FI the SSL check has been added with https://jira.nuxeo.com/browse/NXDRIVE-1647.

the proxy try to anwer gently that the tunnel is not available for https.

this code doesnt not handle the content returned (or the 4xx code) and fail when http

You are right, the check is not ideal. I will create a bugfix ticket and it will be fixed in 4.2.1. Thanks for the report

great support !

Hi [Mickaël Schoentgen](https

Not yet, but you can follow https

Ok, thanks

Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.