-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add a https scheme variable #53
Comments
I'm a bit confused. We have a setting in the config that does this. |
@JulianPrieber where? |
@JulianPrieber i don´t have that option. Nowhere in the admin interface. |
It's right on your config page, |
@JulianPrieber if i go to the url path i get an 404 |
What version are you on? |
@JulianPrieber julianprieber/littlelink-custom:v3.0.0 |
You can check your version at |
@JulianPrieber 3.0.0 |
Then you will have to update to make use of that feature. |
@JulianPrieber that is the latest docker container? |
You can just use the built-in updater in the app to do that. |
@JulianPrieber ok to do this i had to create an installation with an volume mount. to do this i have followed #44. But now i just get "500 Internal Server Error" always i want to access it. |
I do not recommend following the instructions in #44 If you currently don't have persistent storage setup and don't want to lose your data, I'd recommend using the built-in updater. |
@JulianPrieber as i am on kubernetes that is not possible. Also the problem is that the files are not created so i have to create a container without volume and then move the files out and mount it. |
We removed the docker compose example from the config. |
Please add a https scheme environment variable. I always get mixed content errors and it seems like i am not the only one. please add a http scheme environment variable to redirect all links to https.
I also had the same issues like in #44.
The container should create the files by itself and you should not have to make a fancy workaround to get to the files.
The text was updated successfully, but these errors were encountered: