21
Expose AWS EC2 web app via Cloudflared tunnel (lemmy.world)
submitted 2 years ago* (last edited 2 years ago) by to c/selfhosted@lemmy.world
9 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@Lemmylefty@lemmy.world and @voidx@futurology.today !!

all 9 comments

sorted by: hot top controversial new old
[–] 2 points 2 years ago

When it doesnt work, check the log files for the firewall block message.

  • permalink
  • fedilink
  • source
    •
    [–] 1 point 2 years ago* (2 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?

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 years ago (1 child)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (2 children)

    Did you get it to work?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 2 points 2 years ago (1 child)

    OMG I figured it out. It was actually my last comment that got me thinking in the right direction. The problem was that I was using the EC2 public IP address to point the tunnel to. EC2 also has an internal private IP address. Switched the tunnel to point to that, and it works! I felt like such a dummy when I thought about it. The tunnel is trying to hit the app internally. Why would it need to go out to the internet and retrieve a firewalled public address? Seems so obvious now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 2 years 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

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 2 years ago

    He mentioned he was looking at cloudflare logs. So its making an out bound tunnel and when the ec2 firewall is on it doesnt make a connection. If its an outbound tcp connection he should still be able to do a packet capture and see if the handshake is being performed.

  • permalink
  • fedilink
  • source
  • parent