Greetings,
For the last several hours, the following address has returned a 403 Error: https://georgetown-prod.lwcal.com. However, the address that we use for our calendars, events.georgetown.edu, still seems to be fine. Do any of y’all know if this is something we should be concerned about? I know if the second address is connected to the former, but I have half a concerned that our calendars are only currently working due to caching or something like that.
Cheers,
Dash
Hi Dash,
Happy to clarify – your calendar’s -prod.lwcal.com URL isn’t a browser (or cURL) accessible URL, it’s instead just a CNAME that we use for internal DNS routing of your calendar production URL to our hosting resources. So—as long as your calendar is loading fine at it’s normal URL and accessible via the API, SFTP, etc, nothing to worry about. Feel free to send us additional hosting questions or if you run into any issues using the Help Request Form. Thanks!
Karl
Karl,
Thanks for that information. I wonder why it worked until about 1pm yesterday, April 2. We had been relying on it as an address to test with Nagios to try and detect calendar downtimes.
Cheers,
Dash
Huh that is strange! Something internally must’ve changed. I think pointing to your calendar front-end URL is a good alternative for monitoring though (we have a few layers of monitoring we use, and the “outermost” one we just point to that calendar homepage).