Who do I contact about an Apache problem – WordPress.com or URL hosting?

• 

  seagreenzines · Member · May 15, 2015 at 2:15 am

  • Copy link
  • Add topic to favorites

  I have a WordPress.com site – http://www.seagreenzines.com (seagreenzine.wordpress.com – note the missing ‘s’) – with domain mapping from Crazy Domains. I pointed the name servers to WordPress, and everything was working well. As of the past 24+ hours, I can get into my dashboard just fine, but my domain brings up this error:

  Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/1.0.0-fips Server at http://www.seagreenzines.com Port 80

  Who do I ask for help? And, if it’s here, what’s going on with my site?

  The blog I need help with is: (visible only to logged in users)

• 

  jeremeylduvall · Member · May 15, 2015 at 5:20 am

  • Copy link

  Hi!

  The domain seagreenzines.com is loading correctly for me. Are you still getting this error message? If so, can you try clearing your browser’s cache?

  Solve Common Browser Issues

• 

  seagreenzines · Member · May 15, 2015 at 5:30 am

  • Copy link

  Hi Jeremy. I cleared my cache, and that seems to have done the trick for seagreenzines.com The weird thing is that I still get the index error when I tack the ‘www’ on the front (www.seagreenzines.com). Is that normal or something I need to fix?

  Thanks for your time.

• 

  seagreenzines · Member · May 15, 2015 at 5:41 am

  • Copy link

  PS. If I type in http://www.seagreenzine.wordpress.com – I go back to the index error.

• 

  designsimply · Member · May 15, 2015 at 12:47 pm

  • Copy link

  http://www.seagreenzines.com/ should redirect to http://seagreenzines.com/

  New domain settings take time to take full effect in all locations across the world, so if you’ve recently changed settings then it’s probably just a matter of waiting.

• 

  seagreenzines · Member · May 16, 2015 at 3:26 am

  • Copy link

  I’ve had the domain mapped for months now, so it’s not a matter of timing. However, for some reason I can’t fathom, everything is working – including the ‘www’ redirect.

  Perhaps you scared it back to more sensible behaviour. ;)

  Thank you for your time!

• 

  siobhyb · Member · May 16, 2015 at 10:34 am

  • Copy link

  I’m glad to hear this is resolved, my guess is that this was an issue with caching but please do let us know if it comes up again. Have a lovely weekend!