Hmmm, I just tried it again and still got a 404.
PS. This might be the cause of why my node was paused.
Wont have proof since logs are wiped on every version and reset.
I need to figure out how to store logs indefinitely for future troubleshooting purposes.
Here you go:
https://documentation.storj.io/resources/frequently-asked-questions#how-do-i-redirect-my-logs-to-a-file
1 Like
You’re referencing and commit in the git history.
It’s always good to use the last master branch unless that you want to take a look how something was in the past.
Master reference to the directory which contains the document https://github.com/storj/storj/tree/master/docs/blueprints
If I link the document, then it links to the specific commit in master at that moment, so it doesn’t show the last updates.
Discourse replaces github links with permanent links.There are pros and cons to that, what’s referred to will never change so it will always make sense in the context of the conversation. However, documents linked to may be outdated.
Quick update on my situation, there were no failed audits since node was un-paused and score almost at 1 now. This probably means I too was affected by my node never receiving a piece which the satellite was trying to download an audit for.