Fresh install, frontend issues #1819
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1819
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fresh install via docker and as soon as i log in i keep seeing messages in the console and the pop ups stating things like.
when trying to add a task it requires a namespace, so trying to create a namespace throws out error
Not sure what i'm doing wrong and the logs just state something like
Could you share your config and compose file? (Assuming you're using compose)
compose.yml
have other services running that use postgresql and mysql and those were named database and db so in order to prevent collisions i ended up naming it
dbt
- did see in those other db logs attempts from vikunja to auth so that solved it.oddly enough if i look at the site on my phone everything works perfectly, seems like somehow the vue app is weird on desktop?
That definitely sounds odd. As there's some things not enabled on mobile it is still possible that this is a desktop only issue. Do you have the same problems with try?
tried it in different browsers and it works correctly, not sure whats going on with chromium so i guess ill defer to using this on mobile for now.
can provide more details if needed.
In the past there was an issue like this when the user had an "edge-casey" api configuration (a configuration I did not test). The docker compose file you shared does not have that so I'm not quite sure what to look for.
How did you create the user you're logging in with? Through the normal registration flow or with the cli?
Yeah this is weird, ended up using chrome and the problems went away.
Oddly enough in my laptop i still use chromium and it doesnt present the same problems.
Guess we can close this out.