Our wechaty puppet service discovery service has been experiencing out-of-service issues from 11 am Jun 15.
11 am: out-of-service due to SSL cert expired
2 pm: we have noticed this problem in the noon then working on it, and found that the 80 ports of the server can not be reached from the public internet
2:30 pm: the service is back to service by switching to the Heroku Dynos under a downgraded level because we have to use two dynos to serve more than 1,300 concurrency WebSocket connections. You might notice that the token service sometimes returns 404, you can retry 1-2 times to get the right result. (because the token is registered to one server, but not the other)
10 pm: the service has been moved back to the Azure server by creating a new server, which fixed the 80 port unreachable problem. (it might be related to the azure bug because we can not make the 80 port to be visitable from the internet)
Token Service Discovery Service Accident
Our wechaty puppet service discovery service has been experiencing out-of-service issues from 11 am Jun 15.