Ahh, I see you are using Cloudinary image store for Ghost blogs - https://github.com/mmornati/ghost-cloudinary-store . How this related to Surfer, I am still not sure. But are you really sure you want to use that repo? It's not developed for over 3 years and basically unmaintained.

Is this still an issue @hakunamatata ?

IIRC the issues with FTPS where: The modern certs were not accepted by old devices Old devices did not have a way to ignore cert either Have to open a bunch of ports for passive mode Overall, this meant we have to support FTP which is insecure. So, we have decided not to.

@necrevistonnezr THAT is pretty cool. I need to hit those hills more.

@robi Thanks for the tip. I went ahead and add a www record. I believe the templates I am using have it coded into the index.html file. This will work until I spend sometime learning to write my own.

Solved! Hetzner StorageBox accepts ALL transfer protocols so I upload to a StorageBox sub and that sub is connected as a volume to Jellyfin! Perfect!

Ok, thank you!

@girish said in webdav on surfer: @jdaviescoates yeah, that is what is strange. for the client, the access token is no different from a password. there's no difference. I worked it out! When clicking Connect in Nautilus, it wasn't prompt/ asking if I wanted to save my password at all, I was just presented with this: [image: 1697743472696-screenshot-from-2023-10-19-19-23-26-resized.png] And the only thing possible to do when that screen is displayed it to either enter a password or cancel, it's not even possible to view another app or anything. But it seems it should as per e.g. this image from this guide https://www.knthost.com/nextcloud/setup-gnome-nautilus-access-nextcloud-files-webdav [image: 1697742678755-416dd0a1-cd03-4b2d-8786-75293ce3cfe9-image-resized.png] And because I must've chosen "Remember forever" when setting up Nextcloud mount (either that or just adding Nextcloud Accounts via Ubuntu Online Account settings does that anyway), when I tried testing it with an instance of Nextcloud instead of Surfer it doesn't even ask for a password at all. So I figured it must've remember the password somewhere... So I searched for Passwords and found this Passwords and Keys app that I've never seen/ used before [image: 1697743023320-7219f139-e7fc-4d62-8fa4-b67a120cad09-image.png] And I saw there was a pw stored for library.uniteddiversity.coop [image: 1697743084754-4cb386f0-3268-4dc5-b7e4-2de7a6f4dcb9-image.png] But of course that was the old password before Surfer updated to just use access tokens. So I edited the pw to be the new access token, and now it all works again! Phew. And just to test, I decided to try and connect to a Surfer app that I've never tried to mount locally before, and lo and behold this time it did show this: [image: 1697743299687-screenshot-from-2023-10-19-20-20-15.png] Although I note that Nautilus required me to add a Username before being able to hit the Connect button (the button remained greyed out until both a Username and Password were entered into the fields). Anyways, all working again now (and now I now where to find/ how to change the "Remembered forever" passwords too, so bonus!)

Yes your approach seems correct here. Cloudron will not overwrite any existing DNS records, so it is safe to add example.org in this case, even if its used elsewhere.

glad it got sorted out, I guess this can be marked as solved then

@girish thank you!

@msbt alright, then maybe you can give me access to your Cloudron hosting the second test surfer instance, to debug this? If so, please send a mail to support@cloudron.io with your dashboard domain and remote SSH enabled. Also let me know how to exactly reproduce this.

I was able to reproduce @robi 's issue and fixed it. Also the password protection session will not get destroyed on logout.

@d19dotca I'm pretty sure you could still eg follow instructions like these https://docs.hetzner.com/robot/storage-box/access/access-samba-cifs to mount (in this case) a Hetzner Storage box to a dedicated server. The fact it's a physical machine wouldn't make any difference, I think. It's just a matter of telling your machine where the remote drive is and giving it the credentials to access it.

Okay, it's a bit odd since that's the first time I've seen Surfer app crash due to this memory condition, presumably because the GC failed or was started too late with too little overhead available to complete. Have tens of other Surfer apps that do not exhibit this behavior.

https://learn.microsoft.com/en-us/azure/cdn/cdn-how-caching-works is an excellent read on some other interpretations.

@nebulon Thanks for that info!

@Shaun-Snapp Check the logs of the FTP client you use. Sometimes it's set to use a certain protocol or security feature, but over the years that becomes obsolete and is replaced with a new one. You can also try creating a new connection and see if it picks up new settings.

@nebulon Works fine after updating. Thank you!

I wasn't aware of this feature, but it works perfectly. Thank you!