I have just upgraded us from the Launch Plan to the Scale Plan to obtain whatever “Priority Email Support” is. Prior attempts to send emails to the Launch custom email we were given has not generated any replies (usually with ticketing systems I expect at least some sort of auto-reply like: “Thanks for your email, replies should take X hours”.
Our site has been effectively offline for 24 hours with the continued proxy issues. While region swapping has worked, what is now broken is any internal communications of our apps. So any applications which talk using the APPNAME.internal:8080
scheme are broken right now. We are going to swap around to having them talk through the public facing URL which we can thankfully do for one of our applications, since it has both a public facing and internal deployment profile.
It seems this problem is entirely isolated to services which have been deployed in the past 24 hours, other services seem fine and we’re just thankful that nothing has been deployed.
In the support email I gave very detailed diagnostics for the problem:
val http = require('http');
http.get('http://APPNAME.internal:8080/health', (res) => {
console.log('statusCode: ' + res.statusCode);
});
// this prints nothing at all, since it hangs, eventually would timeout like the axios calls we use internally
val https = require('https');
https.get('https://EXTERNAL_DOMAIN.com/health', (res) => {
console.log('statusCode: ' + res.statusCode);
});
> statusCode: 200
This all worked up until the last 24 hours.
So long post, two questions:
- Given we now have Priority Email, when can we expect a reply?
- Why is this still broken? This isn’t a proxy issue as far as I can tell.