When it doesnt work, check the log files for the firewall block message.
this post was submitted on 05 Sep 2023
21 points (88.9% liked)
Selfhosted
39980 readers
780 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 1 year ago
MODERATORS
The EC2 firewall? I was looking at the systemctl logs for cloudflare, so dunno why I didn't even think of firewall logs. I should indeed have done that. Let me check that and post an update.
If nothing shows in the logs, run a packet capture on the ec2 instance and test cloudflare again.
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?
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
Did you get it to work?
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.
Happens to the best of us! localhost or 127.0.0.1 should work too.
I've always personally hated localhost and just opt to use the IP directly, which I guess was my downfall this time :)
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
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.