Selfhosted

42719 readers

1017 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

Expose AWS EC2 web app via Cloudflared tunnel (self.selfhosted)

submitted 1 year ago* (last edited 1 year ago) by chandz05 to c/selfhosted

11 comments fedilink hide all child comments

Hello, I really need some help accessing my app via cloudfared tunnel. The app is installed on an AWS EC2 Debian machine. I can successfully hit the page using http://[EC2IP]:[port] configured via inbound security rules. I can also successfully setup the cloudflare tunnel and access it via that tunnel and my personal domain and CNAME, but ONLY if I expose all TCP ports for 0.0.0.0/0. Otherwise Cloudflare cannot access the application. I have tried adding the public cloudflare ipv4 ranges (https://www.cloudflare.com/ips/) to the inbound rules, but that does not work either. Can anyone help with this?

EDIT: got it to work! Thank you so much @lilshalom@[email protected] and @[email protected] !!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (7 children)

Cloudflare tunnel only requires outbound port opened, check if you've allowed all outbound ports in EC2 security group (the default VPC should have this already).

Otherwise it's probably a misconfiguration reaching the IP/port of the cloudflared service on the EC2. Have you tried checking cloudflared logs? Does your tunnel status show up as healthy?

[–] chandz05 1 points 1 year ago (5 children)

Yep all outbound ports are opened, per default. Tunnel does show as healthy in the dashboard. The cloudflared logs say the tunnel is established correctly but cloudflared cannot reach the application. I only have my home IP address set on inbound for both ssh as well as the application and port I'm trying to access. I'll look into this into more detail again in a couple hours and look at your and lilshalom's suggestions

[–] [email protected] 1 points 1 year ago (4 children)

Did you get it to work?

[–] chandz05 1 points 1 year ago

Not yet. I did a fresh install on a new EC2 server. Cloudflare tunnel seems to be connected correctly i.e. the handshake is successful, and when I hit the URL, I get the cloudflare 404 page that shows the app is down. @lilshalom (is that how you tag in Lemmy?) I'm having trouble figuring out EC2 logs - I'm pretty new to AWS. But I'm pretty confident at this point that the tunnel is setup correctly, but for some reason, it cannot connect to the app. For what it's worth, I did have it all working on my local raspberry pi. I'll tinker a bit more and then I'll probably try the app's GitHub issues page and see if the dev can chime in

load more comments (3 replies)

load more comments (4 replies)