I am tightening up network security on my Yacy node and restricting public access to many of the various .html files (even if they are already password protected by Yacy itself).
Currently the node is flapping between Senior (fully publicly accessible) and Junior (not publicly accessible), and I suspect one of the html files needed to maintain Senior status is restricted.
@Orbiter do you happen to know which html files need to be made available?
Thanks.
Just a guess.
You might also want to try backing off the crawl rate for a bit see if it improves.
If YaCy is crawling aggressively while you’re tightening access, it can struggle to complete peer handshakes in time, which may cause it to flap between Senior and Junior. Slowing the crawl gives it more breathing room to maintain stable connections with other peers and confirm accessibility, without immediately assuming something is blocked.
I have noticed when my system load is at 50% overload I drop in to Junior mode.
/AccessTracker_p.html?page=1
Lists connections and files.
Don’t know.
Maybe api documentation would help. I’d guess that /yacy/hello.html seedlist.* and profile.html would be the important ones.
But if you test and have the results, please publish them here, it may be useful for rest of yacy folks…