+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Account setup (/t-solved-account-setup)
Account setup - zedtheimpaler - 2024-08-09
Hi
I have recently set up jellyfin with my nas and a ubuntu server running docker with Portainer
in the prcoess of setting it up i made a mistake with the container set up and figured it would be easier to start from scratch
so i re did the container in portainer and after it didn't generate the first time admin password
and when i connect to the web-ui it just asks for a username and password (there is no username and password set up)
I have since tried this a couple different ways
mounting the /config
in a different path no luck, The forgot password feature also seems to want my computer to be on the local network but because its a docker container on portainer its not a real Ip address that i could connect a device to access the webui on
I feel like i am missing something simple but I am just not sure on the best way to fix this.
I think maybe i will have to kill the container then remove it then go into the directorys and delete all the data in the ubuntu that portainer is running on and then re-install but im not too sure if thats the best way to go about it
would be great if someone out there could save me some time
thanks in advance
RE: Account setup - Efficient_Good_5784 - 2024-08-09
Try clearing out your browser's cache.
You're not running two Jellyfin server containers at the same time right?
Also, if clearing cache fails, try going to Jellyfin's system.xml file and edit the "IsStartipWizardComplete" to false. This should re-enable the first-time setup screen.
RE: Account setup - zedtheimpaler - 2024-08-10
Hi Efficient_Good_5784
clearing my client cache on chrome fixed it, didn't have to edit any files thank you.
I am a bit curious as to if there was any way it would have worked this out on its own? i missed checking this as with the first instance that i had killed i had tried it on all my devices (that i cared to check) and it showed the same on them too
so seperately samsung interent (phone), Chrome (Laptop), firestick (android).
I am guessing this would have been avoided if i used a different exposed port the second time as it would have loaded as a new page?
either way its fixed so I appreciate your help.
Thank you