Various system issues (DNS, SSL, FTP, etc.) starting May 15

Try making a lookup from this

rem09.rf.gd resolves to 185.27.134.98
 	
Server Type: nginx
 	
No SSL certificates were found on rem09.rf.gd. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server's firewall.```
1 Like

Please create a new topic as the SSL problem here is solved.
Thanks.

2 Likes

You don’t have connected the SSL of yesd you need to wait at least 12h, try reading this

Is not solved

Can please help to reopen the original post I had created?

No, because you created that during the issue. Now its solved (supposedly, some say its working) so you will need to create a new one.
Thanks.

2 Likes

Yes

ok, will create a new post. Or do you mean create a new certificate?

1 Like

Can you move this piece f topic to another topic?

A new post in the forum

:thinking:

FYI @Greenreader9 I’ve been busy with confirming this original issue is indeed closed and had assumed mine was unrelated and opened another thread. However, in light of the following:

  1. My SSL issue started after this post was considered “resolved”.
  2. @aKEtyPho’s identical SSL issue.
  3. Your deduction that my situation is “kind of weird” (in my thread).

Perhaps we cannot confirm yet that this post’s issue is fully resolved? @Admin FYI

Linking mine here as well for others to find:

2 Likes

Linking another seemingly identical SSL issue:

@Admin can we please get your opinion on the matter? I’m patiently waiting but haven’t heard from you in awhile :slight_smile: .

PS found a small difference between my two free accounts that have SSL working and the one that keeps returning ERR_SSL_PROTOCOL_ERROR:

  • Working account are on hosting volume vol10_2
  • New failing account is on hosting volume vol16_2

Maybe has nothing to do with it, just throwing in whatever information I can find :sweat_smile:

1 Like

Try just… waiting

@OverloadedTech I don’t mind waiting, but normally someone in a position to fix needs to first be aware of a problem and acknowledge they are working to fix it :slight_smile: otherwise you’d be waiting quite a long time…

2 Likes

Interesting, @tsemer. It appears that my hosting volume is on vol16_2 and the SSL for it does not work. Hopefully iFastNet and @Admin can keep us updated on this topic.

P.S. I am getting the same error as you: ERR_SSL_PROTOCOL_ERROR.

1 Like

Thanks for bringing that to attention @tsemer and @wackyblackie!

1 Like

What evidence do you have that makes you sure that the hosting volume is the issue?

I’m not saying you’re wrong. But all you have provided so far is your statement than one account works and another account doesn’t, and that the volume is different, and that therefore the volume is the determining factor. Many other things may also be different.

And the fact that hosting volumes only control files, not web traffic.

Here’s another user from vol16_2 unable to activate SSL. Followed all instructons thoroughly (adding CNAME records, Private Key and Certificate in required places) but still seeing these errors:

More than 24h have already passed.

1 Like