Thanks for the reply
Ive tried "disable_startup_check: true" but seems to come up with the same errors. Ill try a few more things then ill re do it all over from the start.
I have 1 more question.
How else are people editing their config files?, because of the permissions I cant edit it within app data, All I can do is edit a file on my machine then copy over the file using the config edit app plugin. Which is also most annoying.
Edit: 10/12/20 - 02:00am:
Mananged to get it working by starting the config conf file from scratch, might of been a space somewhere it should of been but not 100% either way started up the container got to the UI, tried to log in using the display name and password I set in the users_database.yml and It states incorrect username and password with this error in the log:
Getting closer to having it working but im getting blocked at every turn lol. Any ideas?
examples of my config and users database file for ref:
Edit:10/12/20 10:16am
ok so after doing some more fine checking, changed the users yml to this:
also made sure that database_index: 0 was included.
Now when I try and log in it doesnt seem to throw any errors but doesn't redirect away from the login screen. I think I read others were having that issue in this thread so will go back and read up.
After doing some reading I went ahead to the next step with NPM, got my ssl for the domain with lets encrypt fine, added in the info but when going to the domain i get an error to many redirects?
Firefox gives me this:
any ideas?
Update: 12:41pm
after much hair pulling, googling, reading, shooting scrubs on Arma 3. I found out that the ssl/tls settings on cloudflare were the cause of indefinite redirect issues. I can now also log in but am unable to set up the second factor part, I now get this error:
To Overcome this error I continued on as mentioned in an earlier post. I also had to make sure that my container name was changed from binhex-jellyfin to just jellyfin in the protected endpoint config.
now to set up smtp as it trys to send the 2fa setup process via email.
Finally we are getting there
Edit: 11/12/20 13:07:
Ok so all seems to be working well locally.
Now getting a 403 forbidden error when an external ip tries to access example.domain.co.uk.
the address bar changes to > https://example.domain.co.uk/?rd=http://example.domain.co.uk/ and gives the 403 error.
if you manually put an s in making it now > https://example.domain.co.uk/?rd=https://example.domain.co.uk/
it works after that. I read a user a few posts back had this issue couldnt find any fixes for this yet tho?
My settings for NPM are http for my endpoint, and even changing to https doesnt make a difference it still comes up as > https://example.domain.co.uk/?rd=http://example.domain.co.uk/ and gives the 403 error. That ?rd= needs to convert to https but not sure how or where it does that part yet. any ideas?