His_Amor - tunnel issues
This may be due to the fact that we specified the connection port in dinmap not 80, but 8123?
56 Replies
the error you got was very strange and might be intermittent, what happens if you restart the service now?
also try getting the very latest logs by adding
-f to the sudo journalctl commandSorry for the long answer, I just live in Ukraine, you know what's going on here)
Now I will try what you wrote.
no worries, your safety and wellbeing is more important than any of this :)
Thanks)
Pastebin
root@Ubuntu-2004-focal-64-minimal ~ # sudo journalctl -f -u cloudf...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Ah okay, so its trying to hit the origin
http://127.0.0.1:8000 and failing - what does your config file look like?
What is the purpose of the
url: http://localhost:8000 at the top?
The existence of url is making it ignore the ingress rules entirely
You should remove that line
And then add a default service to your ingress rulesI don’t know), I copied the config.yml example from your documentation, I thought that everything was as it should be, you didn’t indicate that you need to change something, I just inserted the rules
Which page? This one? https://erisa.dev/exposing-a-web-service-with-cloudflare-tunnel/
Erisa's Corner of the Internet
Exposing a web service with Cloudflare Tunnel
What if you could host a web service with no ports exposed? With Cloudflare Tunnel, you can!
how to add it?
Because I don't mention
url: anywhere there
Ah that's not my documentation, that's Cloudflare's documentation!
And it's wrong and confusing and I don't like it!
It happens)
by the way
did you mean to put
https on the localhost
because that's not going to work as-isDo we need to specify the dedicated server host?
No.
I just mean that https against localhost won't work like that, if its http and not https you need to change it as such
Good
Try this:
- Remove the top line that has
url:
- Change your ingress to
No(
What's in the logs?
Pastebin
-- Logs begin at Thu 2022-02-24 21:31:20 CET. --Feb 25 19:37:36 Ubu...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
It's still trying to access the
url: http://127.0.0.1:8000 - are you sure you removed that?
What folder is the config.yml in?
I saw a typo localhosst)
Ha yeah sorry I make typos a lot
That shouldnt be related to this error though
worth a try)
Usually the service will load its config from
/etc/cloudflared/config.yml - does that file exist as well?
Also I'm going to delete that screenshot because it shows your servers IP address :)how do i restart services without writing reboot?
sudo systemctl restart cloudflaredYes, please remove it
yes, he is there too
Okay, you should be editing that file instead then
But there are no such settings.
Ok
Copy the contents of your /root/.cloudflared/config.yml to /etc/cloudflared/config.yml
And remember to always edit the /etc one in future
Pastebin
-- Logs begin at Thu 2022-02-24 21:31:20 CET. --Feb 25 19:52:34 Ubu...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
Okay now it's failing trying to contact your actual service you're running that you configured :)
Make sure the services you configured are running and exist
Yes!
You configured something that was running on port 8123 on your server
It's failing to connect to that port
This isn't a cloudflared issue
Ok, I'll try to figure it out myself, thanks for the help.
It worked, thank you very much)
yay!
But, why didn't the ip address change to cloudflare's ip address so that our site would not be ddosed?
You're checking the IP for the main website, not any of the subdomains you just configured
I also connected the website)
It shows as Cloudflare IP to me, the website you are checking from is probably showing an old cached value
Oh good)
You probably shouldn't show so many screenshots of your IP addresses by the way :)
)
You should be okay from what I can see
All your sites look like they are protected
Fine!
Do you want to tell you the story of how our server became on the verge of bankruptcy?
It has 475 players at its peak