I’m still unclear as to how I go about resolving this error message despite reviewing the user guide and forum especially this particular entry: Version 3.0.1 Debian - Oops! Something went wrong!
which I have followed verbatim.
I have checked config.yml and the public URL and port address are correct.
I have re-run the install script using the following command: sudo ./install https://groove-genie.co.uk:8082 --listen-port 8082 --update-nginx in the hope that this would rectify the issue but that appears to have been unsuccessful.
I’m not quite sure what my next step is and wanted to ask can I not just add the url and port address to the config.yml file and re-initialise it?
What is the URL used to access LibreTime in the browser ? This URL should be set in the general.public_url field in the config.yml file.
Your listen-port should only be different from the port in the public_url if you use a reverse proxy between the internet and LibreTime, since the reverse proxy will do the routing from one port to the other. See the newer reverse proxy documentation
You shouldn’t need to configure additional allowed cors origins unless you have a website on some other domain name that consume the data from LibreTime.
From the logs, I understand that you are accessing LibreTime (in your browser) using the https://groove-genie.co.uk url, but you have configured your public url to https://groove-genie.co.uk:8082. So there is a mismatch in the origins.
The listen-port is set to 8082 (as I’m running on the same host as the reverse proxy) so I’ve left port 80 and 443 free. I note the updated reverse proxy documentation and will review the documentation and apply to my configuration (fingers crossed!)
So am I right in assuming if I remove the port address reference (8082) this will resolve the mismatch error?
I have run the install script a number of times incorporating the --listen port 8082 argument and this corresponds with the general.public_url field entry in config.yml.
The Nginx reverse proxy appears to be functioning as expected as I’m able to run nginx -t with no errors and dry-run certificate renewal with no issues; the resulting certificate has been generated and is valid.
I’m completely at a loss as to resolution; if I can’t manually amend CORS what are my options?
Hi Joola,
I did add the additional lines of code to implement the reverse proxy copying the amended libretime.conf to /etc/nginx/sites-enabled/ I run nginx -t prior to restarting nginx at which point I get a failure.
I remove the additional lines of code relating to the reverse proxy and everything appears to function (I’m able to verify the certbot auto-renewal) no joy in terms of CORS authentication.
Here are the configuration files in question:
I know you’ve previously stated that adding https://groove-genie.co.uk to the allowed_cors_origin list isn’t advised but that’s the only thing I haven’t tried so far; I’m wondering whether I should give this a go out of curiosity?
If the default is how would you add additional entries? Can I add additional entries delimited with a comma to the code block in the config.yml file?