XXXXXXX.streamlock.net does not resolve to an IP address. Please make sure your DNS records are set up correctly.
This is the information after checking.
Problem - streams don’t work over https, but they do over http.
Is there a problem with streamlock.net?
info: NS_ERROR_UNKNOWN_HOST
update:
support:
Engineering is actively investigating a StreamLock certificate outage that is causing DNS_PROBE_FINISHED_NXDOMAIN / NS_ERROR_UNKNOWN_HOSTerrors for StreamLock-hosted domains, with highest priority.
The network registrar escalated this already and is working on a fix (it is indeed caused by an error in their DNS).
We’ve opened an incident and are tracking progress on our status page: https://status.wowza.com/cmi5lswv1000pvza5wef0t7di
We will post updates there and in this ticket as we learn more.
Looks like there’s a major issue with their StreamLock certificates and DNS. I’m in Spain and the streaming service has been down all morning and is still not working. I really hope they fix it soon or at least give us an estimate of when things will be back to normal.
This is not ok. All of our streams are down and have been for about 10 hours now. Switching away from streamlock.net to use our own domain and ssl certs.
Hi, same situation here.
It’s been about 10 hours since the StreamLock DNS/SSL issue started and we’re still seeing DNS_PROBE_FINISHED_NXDOMAIN errors across all our StreamLock domains. At the moment none of our HTTPS streams are working.
Support mentioned that engineering and the network registrar are investigating, but there hasn’t been any update or ETA.
Do you have any estimated time for resolution, or any progress you can share?
Hi everyone,
Quick update on the StreamLock situation:
The DNS issue affecting StreamLock domains earlier has now been fully resolved. The outage was caused by an unexpected problem with our external DNS provider, and once identified, our engineering team worked with them to restore the service. StreamLock domains should now be resolving normally again.
If you’re still seeing errors on your side, please try clearing DNS/cache or testing from a different network, as some resolvers may still be holding old records.
If the issue continues after that, please create a support ticket so we can look at your specific domain and setup directly.
You can open a case here: Open a Wowza Support Ticket | Wowza Media Systems
Thanks again for your patience while this was being addressed.
-Vijay
1 Like