After Easy Apache Update, HTTPS works, HTTP does Not

wcs2

• April 11, 2014 23:37

This is such a strange occurrence, I've only found one reference to the problem anywhere and I'm not even sure which subforum here to post it in. But it happened right after I ran an Easy Apache update, so I'll start here: Everything was working normally, but with Heartbleed, I thought it best to update everything. Everything updated normally, but when I visited my primary site on my server (there are a dozen others, but no others have an SSL certificate installed), I found that HTTPS works, but HTTP does not. If it were the other way around, I wouldn't be baffled. Has anyone ever encountered this or have an idea what the cause of it could be? I'd really appreciate any thoughts. Also, if there's a better forum to post this in, please let me know. I'm totally flying blind here. Thanks!

• 

  cPanelMichael

  • April 14, 2014 13:19

  Hello :) Please try rebuilding the Apache configuration file and let us know of any error messages: /scripts/rebuildhttpdconf
  Also, do you notice any difference with using the "www" prefix compared to the non-www prefix when accessing the website? Have you tried clearing the browser cache on your machine? Thank you.

  0
• 

  wcs2

  • April 14, 2014 20:09

  Thanks. THe same thing happens regardless of WWW being entered. It's limited to HTTP vs HTTPS. Only HTTPS works. I'll try rebuilding now and report back.

  0
• 

  wcs2

  • April 15, 2014 15:59

  Sorry for the cliffhanger, it's been that kind of week. Ran the above and it came back with this: Missing owner for domain server1.domain.com, force lookup to root Built /usr/local/apache/conf/httpd.conf OK

  0
• 

  cPanelMichael

  • April 15, 2014 19:17

  That output does not indicate a problem. Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome. Thank you.

  0
• 

  wcs2

  • April 17, 2014 14:10

  Thanks. The ticket # is 4832955.

  0
• 

  cPanelMichael

  • April 18, 2014 15:53

  [quote="wcs2, post: 1623922">Thanks. The ticket # is 4832955.
  To update, we have not been able to investigate the issue due to a lack of access on the affected system.

  0
• 

  aleah78

  • September 15, 2014 04:01

  Hello, I am experiencing similar issues; was this issue resolved and can you make the resolution public? Thank you.

  0
• 

  cPanelMichael

  • September 15, 2014 17:20

  The original poster never perused the issue. Do you notice any output to your Apache error log? Is port 80 open? Thank you.

  0

Please sign in to leave a comment.