UK here so unless I change my country I can’t use it ;)

Well erm yeah… seems to have gone quiet. Cloudflare is a weird beast at times… mind you I’m in the UK which is way weirder!

I have to say that I might be the one here to say something different, but I still use Cloudflare tunnels because I have been with them for so long. I know lots of people hate them, for various reasons, but in this simple example, cloudflare will have many people who have used it, and it really just kinda works. So for getting started, it probably will be easier and quicker… A free account is good enough, will make the services available easily, and is secure enough for most people within reason. Once you are up and running you can change it moving forward.

Forgot to add - Cloudflare also acts as a CDN meaning a slow internet connection isn’t as bad as it could be. This is another reason I like it - it’s free and does help out if you have a slower connection. It isn’t a fix all solution, you still need to ensure that you are protected as well as you can be, have certs, use https, lock the server down as much as you can. Use fail2ban or something similar to stop brute force attacks… do as much as you can to help yourself. But it is easy to use to get you on your way to self hosting, which for me is a win.

Now this I like, just because I have plenty of people who really aren’t techy enough and dislike a lot about the fediverse… I know it’s not for everyone but having a simple front end works for loads! Good work here - I like it, I like it a lot

I run an SMTP relay… very few takers, most just pay for managed email hosting. I run an smtp relay so multiple wordpress sites and services I self host can send mail. My lemmy instance is one

for future reference there are a few ports that need to be open for let’s encrypt to work, and it has a very small timeout (as you have found) so if the dns isn’t great it fails. Cloudflare will cache your site/dns so usually works

It should, and yes I used to think that. I’m in the UK and some routers just fail to work properly with higher port numbers, especially cheap routers from cheaper providers. Once you start getting above 8000 the traffic is limited thus me saying try a lower port number. Plus yunohost doesn’t really ask for a port number as you should add a domain first, then install the application (it uses docker btw) on that domain, then cloudflare to the domain. So the port number isn’t required. I’m guessing, but can’t be sure, that this is the real issue. yunohost adds a self signed cert and configures the firewall etc. so if you don’t do it right using a cloudflare tunnel it just doesn’t work. I’m guessing the OP hasn’t done it like this, and then it will never work - believe me I’ve tried. yunohost also adds fail2ban, firewall inside yunohost and various other ways to protect what is served

Another vote for Immich

It depends… the OP is also using yunohost which can and does have some issues with higher port numbers, plus you also have to factor in if he is self hosting as I suspect, some routers also won’t properly forward higher port numbers either. Difficult to say but lowering the port number is one thing to try. Too many variables to really drill down and say what is happening

Cloudflare won’t connect to a port number that high. Drop it down to say 2536 and you will be fine