Jump to content

j0nnymoe

Members
  • Content Count

    274
  • Joined

  • Last visited

Community Reputation

21 Good

1 Follower

About j0nnymoe

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It's likely you won't be able to reverse proxy an IRC connection (Atleast to my knowledge)
  2. Not normally. But im going to guess you're running with GUI mode enabled?
  3. Wait, penny just dropped, I've been looking at the default file for letsencrypt, not nextcloud itself. Get into the container of letsencrypt and see if you can `ping nextcloud`.
  4. Ok, well looking at your default file, you've added a ton of stuff that isn't need. Confused why you've done that and used the subdomain proxy config aswell. You need to use the supplied default file, you've removed the bit that tell's nginx to use the proxy-conf.
  5. 502 usually means it can't communicate with the container. Is the nextcloud container still on the same custom bridge network as your letsencrypt container?
  6. I only ever recommend network tuners these days. It takes away alot of the stress of getting stuff like this configured, granted it does cost more but in the long run it's much more hassle free. I used to run PCI-e for my DVB-T2/DVB-S2 setup, now I just use a network tuner (Digitbit R1) which TVHeadend controls.
  7. This thread is for users who need support on unraid. Please use our forum or discord for support.
  8. Tested / updated to rc5 myself yesterday and it worked fine. Sounds like the plugin didn't finish downloading the files. Please try it again and check the plugin shows all the files completed.
  9. This needs to be reported upstream to jellyfin then.
  10. Could be a corrupted database? restore a backup of your appdata and see what happens.
  11. You're best to report this upstream to Ombi direct.
  12. When I wrote the article, I'm purely talking about the nextcloud container, Nothing else.
  13. For the time being, we only use the current latest driver that's available at build time.