avinyc

Resolved - set $upstream_app needs to match the container name (in my case bitwardenrs) and I have not been updating all the sections with each updated .conf file. The addition of the location api commands triggered the bad gateway even though others were not necessary. All now match and everything works from web, extension and app. While this is technically a vaultwarden issue, I think it would have been better placed in the swag support thread.

I'm running into a strange 502 Bad Gateway issue with the latest proxy configuration file in swag (so this may be a swag problem rather than a bitwarden docker one). Currently using the 2022-09-08 file version and made my setting changes to the newer 2023-02-13 version of bitwarden.subdomain.conf and the only new changes are the Authentik settings (which are commented out) and the following: location ~ (/bitwarden)?/api { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app bitwarden; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } Everything is exactly the same except for this section in both files, but running swag using this one returns a bad gateway error and my vault is blank when accessing it from the browser. Switching back to the previous conf file, everything is back to normal. Any ideas what's going or if I am missing something else to adjust elsewhere?

For focus, meet, video, and xmpp A75G repositories, I got the following error in Fix Common Problems: (jitsi/jicofo:latest) has the following comments: Latest tag no longer exists on dockerHub Additionally, this application has been blacklisted from Community Applications for that reason. I went to the docker hub for one of them and the tags have changed: https://github.com/jitsi/docker-jitsi-meet The "latest" tag is deprecated and now "stable" is the correct tag. If anyone manages to get this working, they'll need to make those changes in each of the containers. It says CA blacklisted them, so not sure if they will bring them back.

Look in your proxy configuration file "nextcloud.subdomain.conf" You can increase the file size limit. Mine shows as follows "proxy_max_temp_file_size 2048m" Change it to 4096m if you just want to double it to 4gb, or set any higher number and see if that helps resolve your timeouts.

I am not 100% sure this is correct for the nextcloud containers. Official or custom, the containers will update in unraid, but I have not heard of any of them upgrading a nextcloud version automatically. The only way to do that is to manually run the updater from within nextcloud. This extra step occurs with some other containers due to their configuration. I also run plex, and you need to restart the container to run the upgrade process for that one. If there is a container that handled updates and upgrades without user intervention, that would be news to me.

I did not see any discussions about this self-hosted Calendly alternative. I would be interested in running this unless there is a better option already available on unraid. Docker Image: https://hub.docker.com/r/calcom/cal.com/ Homepage: https://cal.com/ Reddit link discussing the docker image installation issues: Curious what other think and if it is worth getting some assistance running it, thanks!

Nope, I'm sure someone would post something if it ever got working. I suspect this isn't a high priority for anyone to fix, and since it operates for those using portainer, nobody is interested in fixing something that isn't broken. I wouldn't mind following the old setup if it didn't cause a daily error in fix common problems.

If you haven't already, I would suggest buying it. The reviews do not match my experience, used this app on iPhone and android for years. Unfortunately, like most here, could not get it to work in docker so running a windows VM with bi ver. 4 and no issues whatsoever. You could get a separate app like TinycamPro, but you will miss out on the recordings and just access the streams live. One annoying issue a while back with the app on android was some update that broke function. I'd recommend keeping an app backup of it if you auto-update to avoid it breaking again due to a bad update. At $10, it is the most expensive app, but it's worth it over time.

Yea I always update through terminal (really think it should be the first recommended option instead of second). Ran into problems with webui in the early days (timeouts and such). Never an issue updating in terminal, just did 25.0.1 to 25.0.2 and all checks passed this round.

Yea, I did pretty much the same as you, but clearly it's something that requires more expertise that simply copying the same settings over. My settings basically match yours (JVB_STUN_SERVERS: meet-jit-si-turnrelay.jitsi.net:443 instead of the google ones you put). But nothing works and I prefer to have everything running through unraid's docker. Maybe this will get someone's attention again for an updated guide.

Is there a reason why we cannot modify the steps to install jitsi using the ones from A75G's Repository? If it can work, the benefit is that they can be updated through unraid's built-in docker like all other containers. I've tried to merge the instructions from this tutorial, but I doubt that is the correct approach. If anyone can share insight or has been able to set up jitsi that can be updated that way, I'd love to know. TIA!

Thank you, this was driving me crazy with the distorted font in terminal/logs. Disabling brave shields was the answer.

I came to this same conclusion for myself as well. I'm glad I was able to configure and get this running, but the update error messages and the large memory usage for something I can simply elsewhere wasn't worth it. I look forward to the day when an all-in-one unraid docker container is created for jitsi.

Seriously? We have to do a fresh install every time this updates? There has to be a better option, no? We can't use recreate in portainer or just docker compose over the old installation?

I'll give this another week or so to troubleshoot and see if anyone is monitoring this topic for support. I have tried multiple fresh reinstalls (both mongodb and rocketchat), checked the port 3000 is not conflicting and open on my router (port forwarding rule set up and checked on https://portchecker.co/ to confirm it is open), tried both SP1 one's rocketchat.subdomain.conf and rocket.chat's doc suggested settings, and set up on cloudflare the proper SRV and TXT records to get green check marks on Federation for everything except the port 3000. I am assuming the reason I can only connect through the web browser and not on the android app is related to this error. I'm clearly making a mistake somewhere or (less likely but possible) this is still a buggy mess to work with reliably. If this is too difficult for me to figure out, I will try setting up matrix, element (formerly riot) and jitsi meet instead. I appreciate anyone taking the time to look at this and let me know if they have any ideas or pointers that could fix this. Thank you!

So I was able to determine the installation with reverse proxy is causing the setup problems. Port 3000 is being refused for connections and it was screwing up the setup wizard's ability to complete. I have a public key auto-generated, but with reverse proxy on, I still cannot get federation to work with port 3000. I have reviewed the SP1 subdomain.conf and the one posted in the rocketchat docs, no clue what I need to do to fix this. If someone has any insight, I would appreciate it. Thank you!

Trying to get federation working with rocket.chat. I have everything running fine with the installation thanks to SP1, but when I go to Administration, Settings, Federation, the Public Key is empty. This may be a dumb question, but the documentation says this is generated by Rocket.Chat, so how do I get it to populate or does anyone know if there is another way to do this. TIA

Thank you so much, these steps are what I needed to remove my last errors and get back to all checks passed. Much appreciated!

Curious how everyone updates their nextcloud with unraid. Mine is still on 20.0.5 and I see 20.0.7 available in the admin panel. I assumed the docker updates would also trigger the upgrades similar to plex, but I see from the first post there are 3 recommended options. Which is the safest approach or is it all practically the same?

It looks like your interface is showing virtio instead of e1000-82545em. If you change CPU and RAM, you'll have to re-run the helper script again. Run it (maybe more than once if it doesn't return a message saying vm fixed) and then start it up.

I still followed SI1's instructions for bigsur (labeled the disk and same settings in the docker) and after I finished with Catalina I upgraded to Big Sur. No issues (but it is another step of course).

So I went into the vm a tried to test safari and of course it was blocked by my router. I had set up access control to prevent new devices from connecting without approval. So turned that off and started this from scratch. Selecting big sur still brings up catalina instead, but no more server connection issues. Will finish the install and see if upgrading through the VM works. My apologies for wasting others time with this stupid mistake on my end. Until the next one!

I've been trying other troubleshooting options. Shutting down my only othe VM and stopping all dockers except macinabox. Still nothing. I tried googling for this error, but none of the solutions work for VM. Clock is set correctly. I don't know how to copy the installer log from VNC (copy and paste doesn't work) but there are errors in there that might be helpful too.

I have a windows VM running as well. That was an easier experience:)

Yes, I also echo my thanks to all those taking the time to help here! I am a complete novice so I would assume I am making some ridiculous error on my end:)