-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
CloudSync begin failed #17315
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
Comments
I managed to find and solve the error. My webdav setup consists of a Synology NAS with Cloudflare tunnel exposing (via proxy) the webdav share for RetroArch to an external domain. For some reason if I try to sync with the external domain in my LAN the sync fails and throws the aforementioned error, but if I try to sync on another network, it works fine. I managed to somewhat "solve" this bug by configuring my desktop computer to use the private IP of the NAS instead of the domain (if I configure it with a NAS.local mDNS domain it also fails), and turning off wifi on my phone when booting up RetroArch. I don't know enough about WebDav nor the specific implementation of RetroArch to know if this kind of behaviour is expected (although finder has no problem connecting via the external domain), nonetheless if possible it might be advisable to throw a clearer and more specific error or warning in the logs instead of the vague |
From what I remember, "begin failed" usually implies some sort of connectivity issues. The WebDav code is indeed a bit of magic, I'll look into it if I get some time. Meanwhile it may be clearer for @warmenhoven |
1.20 adds a bit of logging code so you can get a little bit more insight into failures, but my guess is you won't see a lot of additional logs because it's not actually connecting correctly. You might be able to use tcpdump to see if it's even attempting to connect to the right host. |
I set a https server in ra and logs show ra visit the https address, but it 0% . I checked the log on the WebDAV server it shows ra connect the server with http (iOS) |
If the app is compiled without SSL support then even with an https URL it will not use SSL. |
Just saw your edit; iOS should be compiled with SSL. Can you send the log? |
Sorry, I tried again today, and it's not due to HTTPS. The issue is that synchronization only starts if it's the first sync (or if I delete the previously existing manifest.server file on the server). Otherwise, it stays stuck at 0%. Regardless of whether the synchronization is successful or not, my WebDAV server always shows HTTP, so it shouldn't be an HTTPS issue. logs when there is a manifest.server in webdav server at it stucked at 0%: log of webdav server:
logs when I make a empty restroarch folder on webdav server,it sync correctly:
|
Hi, |
Is there an existing issue for this?
Description
Followed the instructions over on https://docs.libretro.com/guides/retroarch-cloud-sync/ in order to have cloud sync. As far as I can tell I have followed the instructions correctly, and the WebDav share works correctly in macOS finder, but when I open RetroArch a message that says Cloud Sync in progress 0% appears for five seconds or so, then it is replaced with Cloud Sync failed. In order to try and solve this I enabled logging, but only the line
[WARN] [CloudSync] begin failed
appears, which is not helpful. I have also tried this on iOS and the same two tooltips appear. Both were almost clean installs, so it might have something to do with that.Expected behavior
Either working cloud sync or a descriptive error message.
Steps to reproduce the bug
Version/Commit
1.19.1 (Git a0208dd)
Bisect Results
No response
Check in the nightly version
I don't know
Platform & operating system
macOS 15.2
Affected Cores
No response
Environment information
No response
Relevant log output
The text was updated successfully, but these errors were encountered: