All our church webcasts were down this morning at 9 AM

This morning between 8:30- 9:05 AM (and possibly earlier than 8:30), nobody could connect to the RTMP servers. It was an immediate rejection, that the host name wasn't valid (we use OBS which told us). Even when I created another broadcast, I couldn't connect to that either. This affected 3 of our stake's sacrament meetings. Did anyone else face this issue? Do we know what went wrong?

bradpeterson@gmail.com wrote:This morning between 8:30- 9:05 AM (and possibly earlier than 8:30), nobody could connect to the RTMP servers.

We connected for our 9:00 am sacrament meetings without any problem. Perhaps it was a server issue? US West 2 and US Central were fine this morning.

Someone else reported that the staging didn't happen. That is, the server wasn't available until the event start time. Speculation is it was due to daylight saving change last night.

russellhltn wrote:Someone else reported that the staging didn't happen. That is, the server wasn't available until the event start time. Speculation is it was due to daylight saving change last night.

That may make sense. We saw the message change from something about "host not found" to a "can't connect" right at around 9 AM.

Our 9 AM MST event worked fine.

russellhltn wrote:Speculation is it was due to daylight saving change last night.

Last week (not today) we had over a dozen members try to tune in an hour late to their sacrament meetings. I think they may have been on the old transition schedule. After all, it has only been 13 years since the change. [smile]

Maybe they are running Windows XP or Vista?

To avoid problems with our webcasts. I opened and re-saved them. The result was new links. (sigh)

bradpeterson@gmail.com wrote:This morning between 8:30- 9:05 AM (and possibly earlier than 8:30), nobody could connect to the RTMP servers.

Just so we're on the same page, are you referring to Mountain Time or somewhere else?

Mikerowaved wrote:

bradpeterson@gmail.com wrote:This morning between 8:30- 9:05 AM (and possibly earlier than 8:30), nobody could connect to the RTMP servers.

Just so we're on the same page, are you referring to Mountain Time or somewhere else?

Yes, MST. Servers were on US West.

Looks like a similar thread to ours: viewtopic.php?f=27&t=37802

All 7 of our broadcasts Yesterday started their pre-buffer 1 hour before the scheduled start teams (3 meetings pre-buffer started at 8am and 4 meetings pre-buffer at 10am). All 7 on time.

We also had a test broadcast from 7am-8am that started on time to test some audio changes we made in one of our buildings.

All times are MST.

hicksticks2001 wrote:All 7 of our broadcasts Yesterday started their pre-buffer 1 hour before the scheduled start teams (3 meetings pre-buffer started at 8am and 4 meetings pre-buffer at 10am). All 7 on time.

We also had a test broadcast from 7am-8am that started on time to test some audio changes we made in one of our buildings.

All times are MST.

Out of curiosity, when were those events scheduled? Where they all done while MDT was in effect?

For all, it would be good to verify what time zone was selected.

russellhltn wrote:Out of curiosity, when were those events scheduled? Where they all done while MDT was in effect?

For all, it would be good to verify what time zone was selected.

I created all of them Sunday the 25th in the evening. The timezone was whatever the default was for "Mountain Time (US & Canada)".