go69cars Posted December 8, 2023 Share Posted December 8, 2023 Just updated and now I can't access my server remotely. I wasn't using Connect previously but have just turned that on within UnRaid and it seems to be working OK. I can see the dashboard from a remote computer. However I can't access the Server through the myunraid.net link anymore. I checked that my port forwarding is set up correctly. However when I click the check button with in UnRaid I get the following error Sorry, an error occurred The error is: cURL error 60: SSL certificate problem: self-signed certificate I'm not sure how to fix this as I haven't change anything on my end that I am aware of Link to comment
crazyfrenchman Posted December 12, 2023 Share Posted December 12, 2023 (edited) Hi all, I have the same problem. Port open and forwarded. I didn't have the problem before my current version (6.12.6). Before that I was in 6.12.4 (no probleme) then updated 6.12.5 (didn't test unraid.net) then the day after 6.12.6. Edited December 12, 2023 by crazyfrenchman Link to comment
T_Matz Posted December 13, 2023 Share Posted December 13, 2023 Im having the same issue. Unable to connect to Unraid connect. I sign into connect on the server but remote access is disabled, when i try to enable dynamic-uPnP the drop down disappears and is replaced with "disabled - sign into unraid connect to enable" it is a constant cycle (sign in, try to enable, receive prompt, try to sign in... Link to comment
Wizaro Posted December 15, 2023 Share Posted December 15, 2023 (edited) Just curious if anyone found a fix for this, having the same issue with the certificate....Just curious are you guys running Swag? Apparently this is the Curl error code: CURLE_PEER_FAILED_VERIFICATION (60) The remote server's SSL certificate or SSH fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51. Edited December 15, 2023 by Wizaro Link to comment
Solution Trasher Posted December 15, 2023 Solution Share Posted December 15, 2023 I removed the connect plugin and reinstalled it. That worked for me atleast 2 Link to comment
Wizaro Posted December 15, 2023 Share Posted December 15, 2023 Found a solution or work-around that restored my access: Go to Settings - Management Access Change Use SSL/TLS: from "Strict" to "Yes" Not 100% sure if this is the best practice but it did allow me to access remotely after making this change. Link to comment
crazyfrenchman Posted December 15, 2023 Share Posted December 15, 2023 Hello, I have done like @Trasher, remove the plug-in, reinstall it, remove the ssl key and recreate one and re enable remote access. It is working. Thanks @Trasher I should have this idea before reading your post. Link to comment
Trasher Posted December 19, 2023 Share Posted December 19, 2023 On 12/15/2023 at 7:16 PM, crazyfrenchman said: Hello, I have done like @Trasher, remove the plug-in, reinstall it, remove the ssl key and recreate one and re enable remote access. It is working. Thanks @Trasher I should have this idea before reading your post. Took me a 5 hours of troubleshooting and googling before I thought of doing that Link to comment
go69cars Posted December 28, 2023 Author Share Posted December 28, 2023 Sorry it took me a while to circle back to this. I did the same as Trasher and it worked straight away after turning it back on again Link to comment
Recommended Posts