Everything posted by Roxedus
-
[Support] selfhosters.net's Template Repository
Pretty sure its because of the image not being from dockerhub
-
[Support] selfhosters.net's Template Repository
I asked the developer of the container to use a base that implements umask, i will update you on any development on my request
-
[Support] selfhosters.net's Template Repository
I just spun up a new instance of deemix and it went smooth. I also updated the template with the new repo, should be live soon. I dont know how it will treat old installations, @Squid should add a deprecating warning, telling people to use registry.gitlab.com/bockiii/deemix-docker instead of bocki/deemix
-
[support] Vaultwarden (formerly Bitwarden_rs)
This has all the premium features, so yes, it does OTP
-
[support] Vaultwarden (formerly Bitwarden_rs)
Pretty sure the scheme should be left as http
-
[Support] selfhosters.net's Template Repository
From the looks of it, no.
-
[Support] selfhosters.net's Template Repository
Looks like you skipped over the part about downloading the xml, then putting it on your array first.
-
[Support] selfhosters.net's Template Repository
overcome how? the application needs a mysql database connection.
-
[Support] selfhosters.net's Template Repository
@dmynerd78 Seems like you need redis5 with overleaf. there is a few issues on it, check out this issue.
-
[Support] selfhosters.net's Template Repository
hi @isaw Seem like there has been a update for the container since my initial testing. you just need the container port 8080, i will up date the template later today. the warnings you see are supposedly expected.
-
[support] Vaultwarden (formerly Bitwarden_rs)
as long as the domian is resolving to the ip of your reverse proxy, and it uses port 443 locally there is no problem
-
[support] Vaultwarden (formerly Bitwarden_rs)
Personally i have my domain go trough my reverse proxy locally too.
-
[support] Vaultwarden (formerly Bitwarden_rs)
The developers recomend using a reverse proxy for https. https://github.com/dani-garcia/bitwarden_rs/wiki/Enabling-HTTPS
-
[support] Vaultwarden (formerly Bitwarden_rs)
So your domain resolves to bitwardens ip when local? or to your npm instance?
-
[support] Vaultwarden (formerly Bitwarden_rs)
The container doesnt create a self-signed certificate, so it cant serve https over port 443. Can you use the external address locally?
-
[support] Vaultwarden (formerly Bitwarden_rs)
This is the settings I use, this account does not have 2FA enabled.
-
[Support] selfhosters.net's Template Repository
@Mattyfaz i read the issue. I Wil add that path when I am at a computer, or you can create a pull request adding it Doing it now
-
[Support] selfhosters.net's Template Repository
From my limited testing, it does that if the video is in fact set to `max`
-
[Support] selfhosters.net's Template Repository
I am seeing the same. Could you reach out to the developer on Github and raise a issue? Unless this is something @Glassed Silver has told the developer about.
-
[Support] selfhosters.net's Template Repository
@noja @CODEG33K I have updated the template, but you should update yours manually. Edit the container path to be `/app/audio` and `/app/video`
-
[Support] selfhosters.net's Template Repository
Just let me know if you need any changes
-
[support] Vaultwarden (formerly Bitwarden_rs)
I added the following to my reverse proxy for the admin panel location /admin { return 404; } I only access the panel locally using the direct ip.
-
[Support] selfhosters.net's Template Repository
I should stop multitasking
-
[Support] selfhosters.net's Template Repository
I have no idea. Reach out to the developers https://github.com/dani-garcia/bitwarden_rs
-
[Support] selfhosters.net's Template Repository
Did you past the whole log from containerstart in the post?