Closed pushred closed 10 years ago
The server shouldn't ever just "stop" serving a route after it has started. In the current version of solidus I can't think of any reason that would have happened, unless you're using master
and the redirect had an end
Modulus doesn't give us a way to see the contents of a deployed file unfortunately so I have to assume that it's running master. I suspected there was an end date originally but confirmed that in master
one isn't set:
{
"from": "/",
"to": "http://fuse.keithurban.net"
}
It looks like Keith Urban is using version ~0.0.5
, which I believe will use the latest patch version. https://github.com/SparkartGroupInc/keithurban.net/blob/master/www/package.json#L20
Yesterday we experienced an issue on a site where it's
/
path is a redirect. Suddenly the server stopped routing this and began serving a genericCannot GET /
error page. No log messaging was output in the Modulus account where this was served however. Normal page routes worked fine, i.e./home
.A restart of the server fixed the issue so it's possible it's due to a server after a long period of uptime. All metrics looked normal at that point though.
Any ideas?