crusemm

Members
  • Posts

    58
  • Joined

  • Last visited

Recent Profile Visitors

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

crusemm's Achievements

Rookie

Rookie (2/14)

1

Reputation

  1. I solved my Nextcloud issue. I had the wrong Ip address and port. I was using the Unraid IP and the NC port, when I needed to use the IP and port 443.
  2. So how do I get NPM to send the https://nextcloud.mydomain.com to my NC docker? Or how do I get my NC to allow the http to connect through?
  3. From the nextcloud docker From the NPM docker settings from the router Port Forwarding
  4. Are you talking about this? or is there another place to make the change?
  5. So how do I set that up? where is it and what changes do I need to make? Is it a NC setting, or something in NPM?
  6. Server Error 502 Bad Gateway for Nextcloud Running Nextcloud and NGINX Proxy Manager on UnRaid. When attempting to access Nextcloud through reverse proxy, I get a 502 Bad Gateway error. Previously I had Nextcloud setup behind a reverse proxy administered by SWAG. After a server issue in which I had to delete and rebuild my docker image file, I was unable to get SWAG working. SWAG docker is still installed on the Unraid server but is not running. I have since setup NPM to handle the reverse proxy duties. I have my own domain administered by Gandi.net; and I am using Duckdns. I have NPM running successfully with Overseer and Bitwarden (Vaultwarden) dockers and BlueIris running in a Windows VM. I went through the steps in this post 1.) Does the NPM container work? Yes 2.) Is NPM online? "http://XX.XX.XX.XX". Results in the following: HTTPS gets: 3.) Does your target container work? https://192.168.1.220:8666/apps/dashboard/#/ However, http://192.168.1.220:8666 results in 4.) Does NPM reach your target container? However, using HTTPS All the dockers are running on the “Bridge” network. 5.) Another reason could be that you selected the wrong scheme. For example, you used "http", but your target container only supports incoming connections through the scheme "https". I have tried both http and https. I have tried with and without HSTS. 6.) Or you used the wrong ports. So double check your proxy host settings! I have checked the ports multiple times. A weird, maybe related, side note: I cannot enter http://nextcloud.xxxxxxx.xxx , it always gets changed to https://nextcloud.xxxxxxx.xxx
  7. Reverse Proxy issues following GPU replacement Yesterday I replaced the GPU in my Unraid server. When I started up again, Some of my dockers would not start. After a reboot, the docker service would not start. Following the SIO Docker troubleshooting video, I was able to restore the majority of my dockers. I have the following dockers installed: binhex-krusader; binhex-prowlarr; binhex-radarr; binhex-sabnzbd; binhex-sonarr; bitwardenrs; CodeProject.AI_ServerGPU; DiskSpeed; duckdns; Heimdall; immich; mariadb; netdata; nextcloud; overseerr; pihole-template; Plex-Media-Server; postgresql14; redis; swag; syncthing; tautulli; telegraf Of those dockers, I have bitwarden, nextcloud, overseer, and blueiris set up behind a reverse proxy running in Swag. I have swag, bitwarden, nextcloud, overseer, and blueiris all on the same network custom: br0 I can access overseer locally, but nothing else. and I cannot access anything from the reverse proxy. d plexunraid-diagnostics-20240226-2030.zip
  8. Yesterday I replaced the GPU in my Unraid server. When I started up again, Some of my dockers would not start. After a reboot, the docker service would not start. Following the SIO Docker troubleshooting video, I was able to restore the majority of my dockers. I have the following dockers installed: Of those dockers, I have bitwarden, nextcloud, overseer, and blueiris set up behind a reverse proxy running in Swag. I have swag, bitwarden, nextcloud, overseer, and blueiris all on the same network custom: br0 I can access overseer locally, but nothing else. and I cannot access anything from the reverse proxy. plexunraid-diagnostics-20240226-2030.zip
  9. that appears to have worked Thanks for all the help
  10. using Krusader, cannot delete the postgres appdata folder
  11. Kilrah, just so I understand, your saying stop all three containers, remove them, delete their appdata files, then reload all three and start over again? or I only need to do that for the Immich docker?
  12. Yes, I setup redis and postgres prior to. I have removed all three, set them up in redis->postgres->immich order and still have the issue. I can try again though.
  13. When setting up Immich following this guide and this guide. I get an error when I start Immich: [Nest] 602 - 07/21/2023, 2:20:12 PM ERROR [TypeOrmModule] Unable to connect to the database. Retrying (6)... error: password authentication failed for user "postgres" at Parser.parseErrorMessage (/app/immich/server/node_modules/pg-protocol/dist/parser.js:287:98) at Parser.handlePacket (/app/immich/server/node_modules/pg-protocol/dist/parser.js:126:29) at Parser.parse (/app/immich/server/node_modules/pg-protocol/dist/parser.js:39:38) at Socket.<anonymous> (/app/immich/server/node_modules/pg-protocol/dist/index.js:11:42) at Socket.emit (node:events:514:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) My Immich setup has this postgres has this: I have verified the passwords are the same. Not sure where the error is. Any help would be greatly appreciated.
  14. My understanding is, that's how it's supposed to be set. Is there another way that I am supposed to be doing this? Or is there a way to flush this out so the error clears?
  15. Looks like it's Plex, but I haven't changed anything. Best I can tell that's where it's supposed to go.