overview for jrubal1462

Immich is awesome in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 1 points 10 months ago

Oh dang. The applicable parts of that would've saved me a lot of headache. Thanks for sharing.

Google Photos Alternative in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 2 points 10 months ago

I mean, you could still tell them their photos are encrypted 😉😉

(JK I wouldn't)

Immich is awesome in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 1 points 11 months ago (2 children)

I tried the larger file size, but my internet is slow and google kept pulling the plug on my download. Even with a download manager it was un-resumable. Finally, I just re-exported at 2 GB and now I have to babysit the download of 23 different files.

Cloudflare is not working for me the way I hoped it would. in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 5 points 11 months ago

Hey! Running the cloudflare tunnel through systemd right on the machine worked wonders! Thanks! Probably not the most secure way, but at least I know I can play with networks at a later date. For now it appears to be up and running. Thanks a bunch!

Cloudflare is not working for me the way I hoped it would. in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 3 points 11 months ago (1 children)

Thanks. I was hoping (but not sure) that cloudflare would act as a proxy by sending the traffic to the port I wanted, and that would sort things out (since it's all running off of one machine). Still, maybe setting up Nginx is the way to go. I'll have to put that a little ways down the to do list.

Thanks for reaching out, I appreciate it.

Cloudflare is not working for me the way I hoped it would. in c/selfhosted@lemmy.world

[–] jrubal1462@mander.xyz 4 points 11 months ago (1 children)

The logs just say 2023-12-16T03:32:18Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 192.168.1.111:2283...

Assuming it is the problem of Docker containers not being able to talk to each other, I added the option --network="bridge" to the docker command that launches the cloudflare tunnel. Then in the docker-compose file for Immich, I added the line network_mode: bridge to each service. No dice. I think next I'll try installing the cloudflare tunnel as a service directly on that computer.

Thanks for taking the time to help out, I appreciate it.

18

Cloudflare is not working for me the way I hoped it would. (mander.xyz)

submitted 11 months ago* (last edited 11 months ago) by jrubal1462@mander.xyz to c/selfhosted@lemmy.world

8 comments fedilink

Hello all, The first thing I setup to self-host was NextCloud, and I followed instructions and built the stack directly on the host computer. It's hosted on port 80, and I created a Cloudflare tunnel from "cloud.mydomain.com" which points to http://192.168.1.111 and everything works perfectly. I can access the site from wherever, and everything felt great. Now for the thing I really want, an Immich server.

I followed the instructions and set up Immich in a docker container. Everything seems to be working great, I can access it from within my network and backup photos just like I was hoping. Within the same Cloudflare tunnel, I tried to add a new Public Hostname. I want "photos.mydomain.com" to point to the same host but on port 2283. I added the public hostname and pointed it to http://192.168.1.111:2283, but whenever I point a browser there I get the "502 Bad Gateway" error from cloudflare.

I assume this is a Cloudflare configuration issue, but I'm not 100% sure. Do I need to do anyting special with docker if I intend to access it through Cloudflare? I THINK docker is set up correctly because I am able to access the Immich from a different computer on my local network. I thought using Cloudflare made it so that I don't to worry about setting up a reverse proxy. Is that maybe not true?

Or does Immich need something specific to tell it to accept traffic outside of my network? I remember having to set up NextCloud with "trusted domains" but when that wasn't correct, I got an error message from NextCloud, not from Cloudflare.

Any help would be appreciated. I've poked around a bunch and I'm pretty sure I can't solve this on my own.