S3Drive - S3Drive Running on Windows 10 TrueNAS Instance

Ive been working on trying to get a vm to work with Truenas for s3drive syncing and had issues with linux due to permissions being locked on the mounted share. I dont see the same issues on windows so im moving over to a windows VM. This has presented its own challanges due to me running on fangtooth but i got it all prepped and working. Intiailly i was getting this error. On the attached image but after regnerating certs and rebooting im not even seeing any errors when trying to login. I click the login button and it just doesnt do anything. I click signin and the button reacts but it doesnt actually sign me in and no error shows up. Not sure where to get the logs from. I tried build 1.12.1 and 1.12.3

Hi, is it possible that your Windows VM network traffic is routed through some middleware proxy that tries to intercept SSL traffic? Is that VirtualBox, VMWare or any other virtualisation software? Can you try in the Command Prompt running: curl.exe https://auth.s3drive.app/ and see what you get? Since you no longer get the error, but app "stalls" instead (possible indication of network issue), can you visit "About -> Logs" in the app footer and see if there are any entries?

its running behind truenas but i dont have any proxies. also it gives me invalid login when i use the wrong creds it just does nothing when i use the right ones this is my curl command These are the logs.

Thanks for your feedback. We would probably need to try running S3Drive inside VM ourselves. I understand that TrueNAS is the host OS, but what VM software do you use? Is Windows 10 deliberate choice given that it's nearing EOL? Not that there is anything wrong with Win10, but regarding Windows we do the testing on Windows 11 though. (edited)

It's an instance I'm running truenas core 25.0.4 I think it is, fangtooth. I was having lots of issues getting a VM created in the first place so decided to go with windows 10 so I don't have to mess with secure boot and TPM while trying to get it to work. I might spin up a windows 11 VM tonight to try it. Its using incus for its VM management. I'm thinking about ripping truenas off this box moving to proxmox and then running truenas in a VM. I don't know that I would have the same issues if I went that route.

5:50 PM

The setup is really annoying and took me hours so if you are wanting to go that route I can link you to the guide I used to get the VM setup.

Sorry for the delay. In a few days we shall be ready with a new release with couple more logs, which hopefully can shed some light on this.

Hi @cromeanator, actually we've got a new release already available. Please update on your end, then go to App Settings, enable "Debug log" at the bottom, then start the app and try to login. If it works, great, if it doesn't please provide us the logs in a similar way as above (there should be couple more entries). Thanks!

using a clean install of version 1.12.4 build 10120400 downloaded from your website i got this error. It sure looks like its signing me in but right after i get booted. changed my DNS over to cloudflare on this host. still getting no route matched for the curl command which is the same as my desktop thats non virtual and working. i connected to a VPN and it still didnt want to connect. Heres a few more set of logs in order. i killed the app, then launched it and immediately tried to sign in and it did nothing. Just cuz i tried your website and i cant even login there off this machine... it doesnt even bring up the logging in box, when i hit signin nothing happens the button responds like i click it but nothing happens on the page. again that logging in box never shows up. i checked chrome network dev tools and the only thing i can see different between the requests is my client is fetching the refresh token first and then the password. I can send you har files if needed i just need a secure share for them. It also looks like the affected client is passing the APIkey and authorization as the same so API key = 1234123 and Authorization = Bearer 1234123 The screenshot that shows features is the one that worked. Really appreciate your quick responses!

Hmm, that's all quite strange. By any chance, can you check if your time, timezone and/or time server isn't messed up? Refresh token has 1 hour expiry, your clock might be off by an hour if that fails repetitively. You've also had issues with SSL certs, these also don't like time deviation higher than 5 minutes. (edited)

SMH well i feel dumb, i was going to check it again last night but going over the VNC session it was cut off at the bottom and i forgot to check it. Ive had to change the clock on this thing multiple times. I was able to successfully connect so i should be good thank you for all your help!