Duo 1.5.2 - Instance never starts

[dotfortun3-code]

Ever since upgrading to 1.5.2, my instance won't start. When I start the service, the instance begins to start, but Open Sunshine and Pair New Client buttons never enable because I would assume Sunshine is not starting. These are not sandboxed instances.

I have tried connecting to the instance Sunshine instance to see if maybe Duo just isn't recognizing it is started. I tried looking at the event viewer logs, but don't see any errors. I deleted and recreated the instances. I also uninstalled and reinstalled Duo completely. My PC is running 24H2.

I have uploaded the event viewer logs I don't even see Duo log files for the instance I created if they should be in the config folder. Let me know where it should be.

Logs

[bjkheraxd123]

I am not a developer and I am having trouble running the sandbox, but what you wrote does not contain enough information (I use Google Translate) C:\Users\Username\AppData\Local\CrashDumps You can try writing here if you want. I don't know how useful the dump file is. Default port 38299 if you haven't set it from the site set it back

[Black-Seraph]

@bjkheraxd123 He's on the instance settings page, setting the port to 38299 will just create a port conflict, which would guarantee his instance will never start.

@dotfortun3-code Your log is truncated, which means there really isn't much for me to see in it.

Try running the instance for a few minutes, then upload a untruncated log.

[bram-smeets]

Same issue here. It worked once but then I got the steam error (#247 ). After a restart now Duo itself won't start at all anymore. Can't even delete the software. #275

Edit: Link to system logs from when it worked once (sandboxed but with Steam error) all the way up to now
https://www.swisstransfer.com/d/aacf2e6f-b549-4c63-b296-4429e7e6cd9b

[dotfortun3-code]

@bjkheraxd123 He's on the instance settings page, setting the port to 38299 will just create a port conflict, which would guarantee his instance will never start.

@dotfortun3-code Your log is truncated, which means there really isn't much for me to see in it.

Try running the instance for a few minutes, then upload a untruncated log.

Unfortunately I am just an idiot and forgot I changed the password for the streaming accounts. It might be a good idea to add something saying the password is incorrect if possible for people like me who change a password and don't remember to update their password store.

[Black-Seraph]

The age old can't remember my password dilemma. :(

I'll see about adding a test button to the instance configuration page.