AtariAge Posted July 5, 2019 Posted July 5, 2019 Greetings, Yesterday I setup a new subdomain on my site to serve static files, static.atariage.com. The forum is running at https://atariage.com/forums/. I'm using a wildcard SSL certificate, since I have a few different subdomains I use for this domain. I created a new storage configuration for the forum to use this domain: In cPanel, I have the document root for static.atariage.com the same as the atariage.com domain, /home/account/public_html. I setup an A DNS record pointing to the same IP that's used by t he primary domain, atariage.com. I then added this domain to the SSL certificate in cPanel. Here's the domain under Subdomains in cPanel: Once the domain resolved, I updated the Storage Settings for all but one to use this new storage configuration. I then verified that the images, css, and other files were all coming from the static.atariage.com domain instead of atariage.com. This seems to be working fine on the client side of things, however, I am seeing an enormous number of ssl errors in the Apache error log: [Fri Jul 05 15:18:56.991220 2019] [ssl:error] [pid 15248:tid 47353018644224] [client 37.7.161.156:44790] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/ [Fri Jul 05 15:18:57.013118 2019] [ssl:error] [pid 15248:tid 47353018644224] [client 37.7.161.156:44790] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/ [Fri Jul 05 15:19:02.812158 2019] [ssl:error] [pid 21297:tid 47352987125504] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.813747 2019] [ssl:error] [pid 21297:tid 47352987125504] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.813760 2019] [ssl:error] [pid 21297:tid 47352995530496] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.817817 2019] [ssl:error] [pid 21297:tid 47352995530496] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.817817 2019] [ssl:error] [pid 21297:tid 47352987125504] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.817885 2019] [ssl:error] [pid 21297:tid 47353010239232] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:02.817934 2019] [ssl:error] [pid 21297:tid 47352999732992] [client 97.84.73.254:38396] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/35674-ghettopoly/ [Fri Jul 05 15:19:06.684823 2019] [ssl:error] [pid 19068:tid 47352970315520] [client 68.113.94.44:57745] AH02032: Hostname atariage.com provided via SNI and hostname static.atariage.com provided via HTTP have no compatible SSL setup, referer: https://atariage.com/forums/topic/292914-for-sale-random-ps4-games/ I'm not familiar with SNI (not yet at least!), and I've used other subdomains previously. It's possible there were errors with these other subdomains, but none of them see much use compared to this new one I created. This is also a new server installation, and the version of WHM/cPanel is much newer than I was running on the old server for this site. I have posted this on the cPanel forums as well, since I am using cPanel to manage the server, but I'm hoping someone here may be able to shed some light on this issue. Any insight as to why this is taking place and steps I can take to fix it would be greatly appreciated. Thank you! ..Al
Adlago Posted July 5, 2019 Posted July 5, 2019 You are trying to create a cookies free domain. Maybe you should also do for your subdomain Make Primary.
AtariAge Posted July 5, 2019 Author Posted July 5, 2019 1 minute ago, Adlago said: You are trying to create a cookies free domain. Maybe you should also do for your subdomain Make Primary. Can you have two primary domains?
Adlago Posted July 5, 2019 Posted July 5, 2019 3 minutes ago, AtariAge said: Can you have two primary domains? To be a cookies free domain - this domain should be used also as a primary domain
AtariAge Posted July 5, 2019 Author Posted July 5, 2019 Well, I tried to make the static.atariage.com domain a primary domain also, but the "Make Primary" link doesn't actually work. A quick search reveals this bug has been open for a while: https://forums.cpanel.net/threads/cpanel-14652-make-primary-link-fails-on-manage-ssl-sites.619719/ That's unfortunate.
AtariAge Posted July 8, 2019 Author Posted July 8, 2019 I had to back off on this, as it was causing problems for many people, and I'm also unclear exactly why that Apache error was occurring. For whatever reason, the content on the static.atariage.com domain was not loading for some people, and I'm not sure it was entirely DNS-related. I'll probably move this content to a CDN after I'm able to research that a bit more. ..Al
Adlago Posted July 8, 2019 Posted July 8, 2019 1 hour ago, AtariAge said: For whatever reason, the content on the static.atariage.com domain was not loading for some people, and I'm not sure it was entirely DNS-related. Issues for some users of static.atariage.com content may be caused by the cache of their browsers. In my tests on your site - all resources were loaded correctly by static.atariage.com
Recommended Posts
Archived
This topic is now archived and is closed to further replies.