Oh my god I'm stressed

[Admin]

@anon2380157

Kinda same as this. Corrupted install, and can’t connect.

I understand that issue, but what does it have to do with cURL? That issue is caused by either file size limits or script timeout limits, not cURL issues.

So what is this cURL issue you’re referring to?

@adisp007

000WebHost is a main seller. & has only 1 domain ( *.000webhostapp.com ) for their customers.
So it’s easy for them to setup wildcard SSL for that domain. & it become the default SSL for their customer subdomains.

This. Getting a wildcard cert for 1 domain is trivial. Getting wildcard certs for many thousands of resellers, many of which have multiple domain names, is hard.

@adisp007

Of course iFastNet won’t cover/buy wildcard SSL for all domains of their resellers (e.g.: InfinityFree with its *.epizy.com & *.rf.gd domains).
Maybe @Admin should given a suggestion to iFastNet to add SSL menu for their reseller custom domains on their reseller panel (MyOwnFreeHost).

Again:

@Admin

Like the KB article says: we’re working hard to get that. But it’s hard.

Again: WE ARE WORKING HARD TO GET THIS. You want this badly. We want this badly. iFastNet wants this badly. Everyone wants this badly.

But simply wanting something does not make it easier to get it.

Free SSL for all domains is our goal, and is iFastNet’s goal. And WE ARE TRYING VERY, VERY HARD TO GET THIS, but we can’t.

@adisp007

The other solution is to make Let’s Encrypt bot as whitelist bot so the customers can verify their default subdomains to make their own SSL.
Or make InfinityFree SSL tool to support subdomain.

That’s not a solution. If it was that simple, we would have done it from the start.

Getting our tool to allow subdomains is easy. In fact, blocking subdomains was implemented purposely, and removing that check can be done in minutes.

The thing is that WE don’t want to block people from getting SSL certs for their subdomains. The issue is that Let’s Encrypt doesn’t let us.

The reason why we implemented this restriction is because Let’s Encrypt will just not provide these certificates. That’s not something that can be fixed on the InfinityFree or iFastNet levels.

The problem is Let’s Encrypt rate limits. There is a limit on how many certificates can be created for a single domain. If you exceed the limit, no more certificates can be creation.

This limit is enough for “normal” domains, but really nowhere near enough for tens or hundreds of thousands of subdomains.

@HaydenANG

To make an SSL tool to support subdomain, they could Use the freessl.space API.

I looked into that option too. The certificates seem to come from some small Latvian provider. Their APIs are limits are not publicly documented, so it’s hard to say if they are a viable option.

Please do not that their supplier may also have rate limits, but not enough people know about this provider to hit those limits. If we start to officially integrate their service, we may hit those limits too and still won’t be able to get those certificates.

[anon2380157]

@Admin

So what is this cURL issue you’re referring to?

What i mean is Shapely needs Jetpack. But now, i think newcss theme and Pagelayer will be my new solution anyways.

[adisp007]

@Admin

The problem is Let’s Encrypt rate limits. There is a limit on how many certificates can be created for a single domain. If you exceed the limit, no more certificates can be creation.

Oh, I didn’t know about this.
I thought InfinityFree can’t provide it because the admin has not/hardly created the system for their own subdomains.
If like that, so all of resellers are impossible to use Let’s Encrypt for their own domains (for their customers subdomains).

[allroundernaman]

I’m using FreeSSL Space API.

[HaydenANG]

@allroundernaman

I’m using FreeSSL Space API.

@Admin

I looked into that option too. The certificates seem to come from some small Latvian provider. Their APIs are limits are not publicly documented, so it’s hard to say if they are a viable option.

^^

@adisp007

I thought InfinityFree can’t provide it because the admin has not/hardly created the system for their own subdomains.

Yeah, Lets encrypt rate limit these, otherwise someone could (possibly) buy a wildcard for .co.uk, and everyone with a co.uk could get free ssl.

[Admin]

@HaydenANG

Yeah, Lets encrypt rate limit these, otherwise someone could (possibly) buy a wildcard for .co.uk, and everyone with a co.uk could get free ssl.

That’s not quite how it works.

Let’s Encrypt will only issue 50 certificates per Registered Domain. A Registered Domain is a domain which is one level below a Domain Suffix. .com is one such suffix, .co.uk is also a suffix. And epizy.com is a single Registered Domain, meaning Let’s Encrypt will only issue 50 certificates for any subdomain of epizy.com per week.

Let’s Encrypt will not provide wildcard certificates for domain extensions, because domain extensions should never be used to serve a direct website, and any “subdomains” would be owned by third parties. So handing out the full wildcard cert to everyone who owns the domain would make it very easy for hackers to intercept requests to that domain extension.

[HaydenANG]

Yup, I know, I meant to say ‘theoretically’, it’s the same principal, just an incorrect example.

[splash]

Why 000webhost is better than InfinityFree

Thanks for coming to my presentation.

Why InfinityFree is better than 000webhost

• No watermark
• Uses latest version of PHP (7.4)
• Forum community is welcoming
• The Admin is nice
• Admin calls this free hosting, it’s literally premium hosting
• I prefer Hot Cheetos over regular Cheetos.
• Wait, the above one was off-topic, better get back on topic!
• InfinityFree uses iFastNet to power it’s hosting
• Support is actually helpful
• Unlimited subdomains

Thanks for attending my presentation.

[anon2380157]

Seriously?
Someone close this topic please.

[splash]

It’s just my opinion, but the only reason i picked IF is because it had way more features that 000webhost could have, including custom domains and the broken Cloudflare Enabler.

[anon2380157]

Okay then.

[splash]

Zero 24/7/365 support? 000webhost is just not the way to go. 3 GB of Bandwidth, and 300 MB Disk Space for a free account.

Just my opinion, sorry if it offended you in any way.

[Erraticstuff]

that’s why I chose InfinityFree instead 000webhost

[Erraticstuff]

@splash

Why InfinityFree is better than 000webhost

• I prefer Hot Cheetos over regular Cheetos.

...

[allroundernaman]

Exactly.

Summary

I am literally laughing reading this topic, lol from my view 000webhost is nothing in front of IF.