-
Notifications
You must be signed in to change notification settings - Fork 5
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
Unable to connect storage mapping to Nextcloud #658
Comments
Quick update, I did manage to figure out that it's the docker plugin for rclone that performs the connection, and once I worked out how to access it's logs though docker, something I am not too familiar with, I saw this:
Seems it does not like my certificate as it thinks it has expired - this is odd because tests from other machines and also directly on the Kasm machine shows a valid certificate otherwise I'd be having many other Nextcloud problems elsewhere. Unfortunately I haven't been able to find a command to run in the docker plugin to test the certificate like I do using openssl, nor does "bash" seem to work even though the rclone.org site says it should. I can run nslookup and that returns the correct IP for my Nextcloud server. |
I'm still struggling with this, and I just upgraded to 1.16.1 in case something in that might help. All I know is that I need to tell the rclone docker plugin to trust my local CA as the host it runs on already does, or inject the CA certificate into the plugin or as a last resort tell it not to check which doesn't appeal. Anyone? |
Can you double check that the cert on your nextcloud server isnt expired? This log would seem to indicate its expired in June. I'd double check this using command line tools from the Kasm server itself. You don't have any transparent web proxies in your environment that may be intercepting the request do you? |
Yes, I did the test on the Kasm server with curl as well, and I tried it again just now and this is what I get:
What the container log is showing makes no sense which is why I was trying to access the rclone's shell. I do have an HAProxy that's used for external access to my Nextcloud, but the IP above 192.168.1.70 is the internal IP so the curl is looking at what Kasm should be pointing at. I'm writing this reply from within a Kasm Brave browser workspace and it's having no issues with certificates. |
I also tried this to check what the rclone container is doing::
|
I cannot get my workspaces to connect to a configured storage mapping to Nextcloud v30. The provider information looks good when checking against your documentation, I know the WebDAV URL works from a Kasm workspace, and I have recreated the application password for the Nextcloud account I want to connect with to be sure it's correct, but nothing happens and the directly never shows up within my Brave browser workspace.
When I connect with a Terminal workspace I can change to /nextcloud but a directory listing returns:
ls: reading directory '.': Input/output error
I cannot see anything logged in Kasm and nothing is being logged on Nextcloud even though with tcpdump I see connections from Kasm to Nextcloud, so the traffic is flowing. Both are on my local network and are separate machines.
Is there some logging setting I am missing to be able to trace what Kasm is doing?
The text was updated successfully, but these errors were encountered: