104.156.48.29

Hello all,

We are finding some last minute issues with site content, so I think we'll need the rest of the day to get that corrected, and plan to launch tomorrow.

Thank you,
Connie

I just updated the A record in Godaddy for dioceseofscranton.org to 104.156.48.29

Ryan,

We are seeing the following behavior:

https://www.dioceseofscranton.org is being redirected to https://dioceseofscranton.org and then we are getting a cert error.

image.png 51.5 KB • Download

1) The old site didn't use www., did it?
2) Have you cleared your cache?

Yes and yes

Very strange.  I for the life of me can't figure out how you would get the SSL error, but no one else (to my knowledge) outside the building.

I did switch the site to use www.

I'm going to fix the redirects now

Ryan,

I am not seeing any issues now, but several others still are.

It might be an internal DNS caching issue.  I had to update our DNS zones on our internal DNS servers too.  I'll ask everyone to reboot.

Ryan,

Can you check on the redirects for cssdioceseofscranton.org?

For example, cssdioceseofscranton.org/content should be redirecting to 
www.dioceseofscranton/css/home/about/

Brent had uploaded this spreadsheet with the redirects last week

List of Redirects from cssdioceseofscranton-org.xlsx 10.8 KB • Download

Yes, I'm looking into this right now.  The CSS redirects aren't working for some reason.  The other redirects are working properly.

CSS redirects have been repaired and working properly now.

From: Lechleitner, Melissa <mlechleitner@dioceseofscranton.org>
Sent: Wednesday, February 13, 2019 2:50 PM
To: Wisdo, Connie <cwisdo@dioceseofscranton.org>
Subject: RE: New Diocese of Scranton / Catholic Social Services website is live

 

 

that’s the email address that is posted throughout the website…on the left side of the footer, within the details and directions blocks.

 

Oops

Yikes.  Yep this was a mistake when I did my find and replace.  I've fixed these so all Programs and Offices are back to normal.

I have also just updated the Editing Guide to display where and how to edit the DOS & DOSCSS footers.

https://docs.google.com/document/d/1nE46arTc1gW40Gy7w5iXHVr_toopx52aoyyaQYmc3UY/edit#heading=h.byk4y11yjrrl

Ryan,

We have other domains:
dioceseofscranton.net
scrantondiocese.org
scrantondiocese.net

Would I be able to point the "@" record to 104.156.48.29 for these domains as well?  We just had them "parked" previously.

Thanks for all your help yesterday!  Feedback has been very positive on the site so far.

Connie

Connie,

Absolutely!

I'll add them as aliases.  The only thing worth noting is that I won't be able to update the SSL cert until all three have propogated.  In the interum you may see that "security" warning again if you use any of those three.  

That shouldn't take very long, and they'll be secure once I issue a new SSL that covers all 5 domains. The other domains (dioceseofscranton.org and cssdioceseofscranton.org) won't be impacted.

Ryan,

I've updated the A records for dioceseofscranton.net, scrantondiocese.org and scrantondiocese.net.

Sorry for the delay.

Connie

No worries here.  I see they have all propagated already, so I went ahead and updated the SSL cert to reflect.

Hi Ryan,

I have just a few additional requests for redirects.  I'm sorry to keep bothering you with these...

/an-ecumenical-celebration-of-the-word-of-god-2019/ to 
/media/ctv-catholic-television/view-ctv-programs/an-ecumenical-celebration-of-the-word-of-god-january-24-2019/



The following are as a result of a "parent" page change:

/child-protection-victim-assistance/training-adults-and-youth/


On the original list but not working:

Strange...  I've attempted a small handful of different ways to code the re-writes for the three that aren't working.  It seems there's something else going on somewhere down the line with these.  Nothing is making sense with these!

Connie,

I've circled back to this and added the new one and the couple adjustments to existing ones.

On Friday you reported three that weren't working.  I tested them on Friday and they were not working for me either.  I saw no issues with how they were written, and couldn't figure out why they wouldn't work.  For all intents and purposes, they should have been working.

Today, I tested again, and like Friday they weren't working.  I started moving them around in an attempt to isolate and identify the issue.  The good news is, they are all working now!  The bad news (sort of) is I still don't know why they weren't working initially.  Generally it's easier to accept a solution if I know what the root cause was.  This is a case where the root cause is unknown, and I'm going to leave it that way since things are working as expected.