The SUBCLUB now has SSL support -- FINALLY!!!

[Deezfluffybutternutz]

I came here from a search and wanted to to chime in with some info.

It wasn't working in my Chrome Android until I turned on my VPN. It probably started working since it uses a different DNS lookup.

 

[loccdor]

It doesn't work from my workplace on or off their VPN using Windows and Firefox or Edge.

It works from my iPhone and Safari and no VPN.

 

[NigelR1000]

I have just come to this thread on Chrome on a PC in the UK and I cannot access Subclub with any of the links shown in the post. I do collect subminiature cameras http://www.nigelrichards.org.uk/photographica/index.htm this is my very old http website. I have avoided going to https because ..........
Just also tried accessing via VPN to Seattle without success.

 

[koraks]

Welcome aboard @NigelR1000! I can visit your website just fine. It may be advisable to add https still, since (1) search rankings will be affected and more importantly (2) many platforms will now or in the future simply refuse to show non-secure content.

 

[NigelR1000]

I created the website in 1998 when work asked me to be webmaster of the corporate intranet and I knew nothing about building web sites (I was a Systems Analyst), building this site kept me one step ahead of the customers... I have been saying for 20 years I should redevelop it however as always time is a factor. I do more photography and repairs than collecting now. http://www.nigelrichards.org.uk/ is my photography site. Shame I can't access the SubClub. Cheers

 

[grahamp]

The subclub links are showing an expired (since September 2025) SSL certificate.

Chromium is being its usual inscrutable self, but Firefox let me bring up the certificate details.

 

[Minolta93]

I still cannot access it from California.

 

[xkaes]

Your best approach is to use a VPN or private tab. I'm still working with the NEW host company to figure out the problem -- my New Year's Resolution.

 

[Minolta93]

C:\>ping http://subclub.org                                                           
Ping request could not find host http://subclub.org. Please check the name and try agai
n.                                                                                     
                                                                                      
C:\>ping https://subclub.org                                                           
Ping request could not find host https://subclub.org. Please check the name and try aga
in.                                                                                   
                                                                                      
C:\>ping https://www.subclub.org                                                       
Ping request could not find host https://www.subclub.org. Please check the name and try
 again.                                                                               
                                                                                      
C:\>ping www.subclub.org                                                               
Ping request could not find host www.subclub.org. Please check the name and try again.
                                                                                      
C:\>ping subclub.org                                                                   
Ping request could not find host subclub.org. Please check the name and try again.

Just some more info for you if it helps. I haven't tried using a VPN yet. Near San Jose, CA at the moment. AT&T is my Internet provider.

 

[aconbere]

C:\>ping http://subclub.org                                                          
Ping request could not find host http://subclub.org. Please check the name and try agai
n.                                                                                    
                                                                                     
C:\>ping https://subclub.org                                                          
Ping request could not find host https://subclub.org. Please check the name and try aga
in.                                                                                  
                                                                                     
C:\>ping https://www.subclub.org                                                      
Ping request could not find host https://www.subclub.org. Please check the name and try
 again.                                                                              
                                                                                     
C:\>ping www.subclub.org                                                              
Ping request could not find host www.subclub.org. Please check the name and try again.
                                                                                     
C:\>ping subclub.org                                                                  
Ping request could not find host subclub.org. Please check the name and try again.

Just some more info for you if it helps. I haven't tried using a VPN yet. Near San Jose, CA at the moment. AT&T is my Internet provider.

Ping is increasingly a poor tool for this as so many hosting providers block icmp requests at the gate. The error is hostname resolution, you could try querying some common name servers (dig and nslookup are examples of tools for this) and see where the name is getting lost. You might have a local name cache at your home router, and/or one provided by your ISP, but you can also try cloudflare’s name server at 1.1.1.1 or google’s at 4.4.4.4

 

[koraks]

Ping is increasingly a poor tool for this as so many hosting providers block icmp requests at the gate. The error is hostname resolution, you could try querying some common name servers (dig and nslookup are examples of tools for this)

Yup. Btw, I get perfectly fine DNS resolution with ping on www.subclub.org

> ping www.subclub.org
Pinging www.subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.

>ping subclub.org
Pinging subclub.org [69.49.101.19] with 32 bytes of data:
Request timed out.

Then again, I can also access the website just fine.
I notice that the server this domain is hosted on refuses all sorts of diagnostics; they're relatively restrictive and basically wayward at handling this.

I haven't tried using a VPN yet.

You could give that a shot.

The real solution is for @xkaes to fix https.

I'm still working with the NEW host company to figure out the problem

This is a routine task for which virtually all hosting providers will have a how-to guide set up. If you have little/no experience setting these things up, it's still a routine question for them and with a little back & forth with them, it should take less than 48 hrs to fix this. If you're capable of following a user guide, it should be fixable within an hour. This is just to let you know that it's not very complicated or a daunting task. You can do this.

PS: @xkaes while you're at it, you may consider removing the spam from the bottom of your home page.

 

[Minolta93]

Since my ping didn't work at all, I tried using the

tracert

command--but this time it resolved the IP address (37.16.0.118).

I tried to access the site again through my browser and still couldn't access it.

An error occurred during a connection to 37.16.0.118. Peer reports it experienced an internal error.

Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.

I tried

ping

again:

C:\>ping subclub.com                                       
                                                           
Pinging subclub.com [37.16.0.118] with 32 bytes of data:   
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54           
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54           
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54           
Reply from 37.16.0.118: bytes=32 time=8ms TTL=54           
                                                           
Ping statistics for 37.16.0.118:                           
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),   
Approximate round trip times in milli-seconds:             
    Minimum = 8ms, Maximum = 8ms, Average = 8ms

Finally, I turned on a VPN using a server in Finland, and I was able to access the site.

I have no idea what your problem could be but maybe some of this helps.