[fixed] CentOS stream 9 Linux first login - Unexpected error CurlError: 60

Im using CentOS stream 9 x86_64 kernel version 5.14.0-402.el9.x86_64.
I installed the repo key and repo and used dnf to install the rpm, which all worked fine.

When I run Insync and try to login on using the web method it just hangs. If I use the alternative method with key from google drive I get ;

Unexpected error CurlError: (60, ‘SSL certificate problem: unable to get local issuer certificate’)

I removed the package many times and retried many time with no success.

I am having the same problem with 3.8.7.50508. I am packaging it for NixOS, using ubuntu binary package:

INFO     2024-01-07 19:01:58,517 [httpclient:request:192] Curl error CurlError(60, 'SSL certificate problem: unable to get local issuer certificate') while requesting to 'accounts.google.com'.

fixed with new update to insync-3.8.7.50516 . . . Thanks!!

1 Like

Thank you for the update, @ryjguy7 ! :slight_smile:

@hellwolf, let me know if updating to the latest version resolves the error.

I am getting new errors:

js: Failed to load https://app.posthog.com/decide/?v=2&ip=1&_=1709337015547&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.

Hi @hellwolf, I will raise this to our engineers for investigation. Just checking that this happens on 3.8.7.50516?

Hi, I’m getting the same error as hellwolf. My logs are below:

QQuickWidget::invalidateRenderControl could not make context current
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
INFO     2024-03-27 18:01:55,598 [mainlogs:_log_run:138] Core(app_version=3.8.7.50516, platform=Linux-x86_64-ubuntu/22.04) initialized
INFO     2024-03-27 18:01:55,611 [mainsettings:_load_settings:236] Loaded settings, machine fingerprint = NORebR9IC9qdKyVOTgjm8BX3BqY=
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
QQuickWidget: Failed to make context current
QQuickWidget::resizeEvent() no OpenGL context
QQuickWidget: Failed to make context current
INFO     2024-03-27 18:01:55,682 [app:start_core:65] core started
INFO     2024-03-27 18:01:55,684 [unix_socket_server:start:106] unix socket server thread start
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8)
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
QQuickWidget: Attempted to render scene with no context
QQuickWidget: Attempted to render scene with no context
js: Failed to load https://app.posthog.com/decide/?v=2&ip=1&_=1711562515881&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 6000
js: Failed to load https://app.posthog.com/e/?ip=1&_=1711562515998&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 6000
js: Failed to load https://app.posthog.com/decide/?v=2&ip=1&_=1711562516026&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 6000
js: Failed to load https://app.posthog.com/e/?ip=1&_=1711562518886&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 6000
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
qt.qpa.backingstore: composeAndFlush: makeCurrent() failed
js: Failed to load https://app.posthog.com/decide/?v=2&ip=1&_=1711562515881&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 12000
js: Failed to load https://app.posthog.com/e/?ip=1&_=1711562518886&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 12000
js: Failed to load https://app.posthog.com/e/?ip=1&_=1711562515998&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 12000
js: Failed to load https://app.posthog.com/decide/?v=2&ip=1&_=1711562516026&ver=1.26.0: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'file://' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Bad HTTP status: 0
js: Enqueued failed request for retry in 12000

This is on a fresh install of Ubuntu on WSL:

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.4 LTS
Release:        22.04
Codename:       jammy

Version info:

❯ insync version
3.8.7.50516

I’m a long term user, and its quite important to my workflow, so happy to help out with the investigation in any way

Just to note, on a different machine using WSL I have insync version 3.7.12.50395 installed, and its working fine. I don’t have a way to downgrade to this version on my new machine though - if there was a way to do so that could provide a temporary workaround while this issue is being resolved

Hi @seanmcloughlin! Before downgrading, may I ask you to quit Insync then collect the logs.db and out.txt files from ~/.config/Insync? Then, please send it to support@insynchq.com with the link to this Forums post.

You can try to downgrade to that version by going here: New Insync version: 3.7.12. Let me know if you encounter any issues with this build. Thank you!