Well yep, was just trying to be helpful and test the beta, not for me then I guess, as you were. 
1 Like
They said your input was valuable, we’ll see what they do it with it over time.
Thank you.
Any feedback, from those who can test or those who can’t, is valuable and we appreciate it all.
We wish we were able to account for every possible deployment scenario during this beta phase, but we obviously missed a few. We want everyone to be able to use the service if they want to and will be prioritizing that going forward.
Also having this issue… Def using port 443 for my server as well. Running RC1 shows connected and healthy on my server but connect gives connection error in Connect.
same here. running caddy in docker (or any http proxy) on 80/443, move truenas to 7080/7443, cannot use trueconnect, the dashboard just errors out gathering the initial information
Glad I found this thread. Same issue – I do not have this running on port 443 either. I hope they give us some workaround.
Well my request was closed, so no way to tell really.
Thanks for the feedback everyone. A new version has been pushed to production that includes support for non-standard ports! We are working on streamlining this process in future NAS releases, but we have to work with their release schedule.
If you want to use a non-standard port, add the system to TrueNAS Connect as you normally would, select “edit”, and then define your port.
Appreciate the feedback for this one, and happy to get it taken care of.
Continue to let us know your thoughts and feedback.
2 Likes
Great news! As soon as the hotfix for SMB is released I will update back to 25.10 and try it out.
Ok I got this working, but only my root user can login, is that by intention?
other users just get credentials errors, with known working credentials. Permissions problem maybe?