SUMMARY I'm uploading photos to SmugMug. I've successfully uploaded around 1600 or so. I have fairly frequent intermittent failures, with messages like "illegal value" or "connection closed". In each case, I've visited the SmugMug API page and verified that the API is up and functioning. STEPS TO REPRODUCE 1. Upload some photos, 10-15 or so. Repeat as necessary until ... 2. Eventually, after some random number of photos, uploads will stop working 3. OBSERVED RESULT Uploads stop working with the above error messages. Checking the API on the website validates that the API is up. Logging out and back in doesn't fix. Rebooting doesn't fix. Revoking the digiKam API access on smugmug.com and re-establishing it with digiKam doesn't fix. EXPECTED RESULT Successful uploads. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: I don't know how to find the above on my Linux Mint system. Here is info from the flatpak: Version: 7.1.0 Last Updated: September 6,2020 Runtime: org.kde.Platform/x86_64/5.15 ADDITIONAL INFORMATION
SmugMug is not free and our account has already been deleted (after 14 day). So we can only test it badly. Please post the debug output from the terminal if the problem occurs as described here: https://www.digikam.org/contribute/ Don't forget to set the debug environment variable. Maik
Created attachment 136881 [details] Debug output - 7.2.0-rc I couldn't figure out how to get debug output from 7.1, on Linux Mint it's installed as a flatpak which makes it stupidly hard to get CLI access.
>on Linux Mint it's installed as a flatpak which makes it stupidly hard to get >CLI access. This is why we promote and support AppImage bundle instead flatpak https://files.kde.org/digikam/ Gilles Caulier
Yesterday I ran wireshark to see what's happening under the hood. It's all HTTPS and I don't (yet) have a proxy set up with a fake cert to decrypt, so I couldn't look at the API requests / responses. I did see a ton of RST packets coming back from the AWC EC2 instance that SmugMug is using for storage. I stupidly didn't save the capture for you, but I'm sure I can reproduce it; I'll attach a capture as soon as I have one.
(In reply to caulier.gilles from comment #3) > >on Linux Mint it's installed as a flatpak which makes it stupidly hard to get >CLI access. > > This is why we promote and support AppImage bundle instead flatpak > > https://files.kde.org/digikam/ > > Gilles Caulier Ha! It's sad, really. Flatpak is supposed to enhance security, but it seems to me to end up as a self-inflicted DoS attack. :-)
AppImage = simplicity => efficency and work in main use cases, but less secure. flatpack = more complex but secure, but finally, do not do the job... We use AppImage to publish daily a quick version usable and testable as well. If you want secure version, the native package must do the job in fact. We already see plenty of wrong user report about flatpak. This is why we continue to support AppImage, because after all, it work as expected... Gilles Caulier
Created attachment 136882 [details] Wireshark pcap - SMugMug upload failures 192.168.1.106 is me. The filter I used was "host upload.smugmug.com", which resolved to 54.225.173.48 at the time of the capture. A reverse lookup resolves to ec2-54-225-173-48.compute-1.amazonaws.com, which I assume is what SmugMug is using for storage. Towards the end of the capture there's a flood of RST packets from the EC2 server back to digiKam. This happens on a random basis - time of day doesn't matter, number of photos I'm trying to upload doesn't matter.
*** Bug 471451 has been marked as a duplicate of this bug. ***