Public URL set but error remains

Support
1

Hello!

I’m trying to install Vikunja with podman, and I’ve been following along with the docker instructions. There were some folder permission issues that I believe I’ve resolved at this point, but I am now stuck with the error level=ERROR msg=“service.publicurl is required when cors.enable is true”.

However, I am using the default config file and have specified the server’s IP address (“http://192.168”…etc) in the config file (and I do get the INFO message “using config file: /app/vikunja/config.yml”, so it appears to find it). I also tried setting the public url as an environmental variable, but I’m still running into the same error. Any ideas?

2

The correct env variable name is VIKUNJA_SERVICE_PUBLICURL.

So it should be something like http://192.168.0.101:3456 and the 3456 port should be exposed too.

3

Thanks for your reply! I did try it with the appended port number and using the VIKUNJA_SERVICE_PUBLICURL env variable before, and I double-checked again just now, but I still get the error.

I made sure the port is available with ufw allow 3456

4

Maybe you can either use config.yml or env vars? Try looking it up.

5

Good idea. I’ve tried using the env variable without setting the config and allowing it to use the default, and I still get the error. I originally tried without setting the env var and running the config file, but now I’ve now also unset the env var and tried to run it with the config file. Same issue.

I’ve been trying to set up Vikunja on and off for the past week but I seem to be really stuck with this one!

6

Do you see HTML saying “We’re sorry but Vikunja doesn’t work properly without JavaScript enabled“ when doing the following command from the host server?

curl http://localhost:3456

If so this means the port is exposed correctly from the container. If not - might mean that port is not exposed from container.

Also “service.publicurl is required when cors.enable is true“ means code simply fails to read the service.publicurl parameter - double check if the syntax is 100% correct in config.yml.

I haven’t worked with Podman before but I assume it shuold have something like docker-compose.yml for stack configuration? If so please share the contents of this file.

Also double-check file permissions of the config.yml and directories that contain it if any - I guess you shuold be mounting the directory/file into container somewhere. Even though it says it reads config.yml from my experience does not nesseseraly mean it reads your file, could be reading the one built-in the Docker image.