My wife hates typing “vikunja…” and asked if we can just call it “vike”. I’m self hosted, so in config.yml I just changed “publicurl” value to an array:
publicurl:
and to my pleasant surprise, both hostnames now work fine! (With DNS CNAME created, obviously).
As expected, most data & preferences are the same regardless of login domain.
However, I noticed that the “Last Visited” projects list was different under the new hostname; after a bit I realized it was cleared upon each logout. But now I’m unsure whether that was always the case??? I use the “Stay Logged In” and realized that I basically never log out. I had assumed the Last Visited info was persistent across sessions…?
So my Question… are the Last Visited project cards relevant only to the current login session by design?
Anyway, I continue to love Vikunja, much more usable than commercial offerings! Thanks for listening!
Hey 
Using multiple urls is not officially supported. It’s interesting that you got it somewhat working by just switching to an array.
What about adding a redirect in your proxy?
I wondered if it might be the case that this wasn’t official/intentional.
At this point, I don’t have a proxy in front of it. (I had a cloud server I was about to destroy, then thought I’d try Vikunja on it first, so did a minimal setup. Fell in love w/ Vikunja immediately, still running on the temporary setup…)
Sorry I can’t really investigate much at this time… all I did was was create a Vikunja service (on ubuntu) per instructions, set “interface: 80” and used the existing pgsql instance on that machine. Been flawless ever since 
.
I’ll let you know if I have any updates; I’m going to leave publicurl multi-valued until/unless it creates problems. I like “vikunja”; my wife likes “vike” 
Hey there @Tengammaps, how did you get this to work?
I have added this to my config.yml file:
service:
publicurl: [ "https://vikunja.mydomain.com", "https://test.mydomain.com" ]
But when visiting the second domain I get asked to login (even when visiting shared projects), which then doesn’t work. How did you get around this?
I am running vikunja behind traefik (Reverse Proxy). Even tried spoofing the host-header, but vikunja is probably using a different header / window.location to determine the Instance Host.
Turns out I needed to add the test domain to cors.origins (also an array)
So sorry I didn’t respond to this sooner, but I’m glad you got it working!!!
I imagine your cors.origins discovery will help me in the future, when I put Vikunja behind a reverse proxy myself - thanks!!!
1 Like
Newest Update seems to have broken this, it won’t startup unless service,publicurl is set, which it is, but because it is an array and it is expecting a string it then exits with an Error.
version: 1.0.0-rc2