This issue has been around for over a year now, and still persists. Not sure what the exact criteria are, but LP will not route through a tesseract if I log out and back in, and oftentimes will refuse to connect again unless I break both tesseracts, poes, and then place them in some random order that doesn't stay the same each time. I've tried every combination of placement, but it seems to not want to route through the tesseracts anymore from then on, until server reboot, and I place the tesseracts again.

Not sure if this is part of the issue, but I did lock them with signalum, and have them set to 'restricted' mode.
The proxy is loaded and enabled, doesn't have any error messages that I can see, but this time around I'm not the server admin, and have no access to server logs unless they're fed to me when something crashes.

Some info:
buildcraft-7.1.17
buildcraft-compat-7.1.5
CoFHCore-[1.7.10]3.1.3-327
CoFHLib-[1.7.10]1.1.2-182
logisticspipes-0.9.3.126
ThermalDynamics-[1.7.10]1.2.0-171
ThermalExpansion-[1.7.10]4.1.4-247
ThermalFoundation-[1.7.10]1.2.5-115

I'm wondering if it has something to do with chunkloaders, as the two remote places that have a paired tesseract have a spot-loader. We're using chickenchunks.

Okay, nevermind. it has everything to do with restricted mode. If I change the tesseracts to public, they work fine again, and seem to survive a logout. However, this does lead to an issue, that if someone else jumps that frequency, I'm hosed.

Is there some way to add LP to the "/cofh friends gui" so that tesseracts can be used in restricted setting for servers? or any way for LP to detect that its connected via the tesseract and just bypass the interaction with the tesseract, and just move the item to the pipe?

This seems to occur with public channels too. So the above is possibly irrelevant.

Considering that the LP pipes do connect until I log out and the chunks are unloaded, I would assume that LP can infact route on its own.

Perhaps LP could save this information in a permanent, chunkloading-safe way, and load it up next time "boots" on reload, and only change the saved data if it detects a tesseract being placed/broken beside it.

Considering I've been messing with this for 3 days now, and have noticed several aberrant behaviors from several mods and even vanilla contraptions, along with knowing that weird issues with various things have been going on for a while now, I'm now thinking that the issue has something to do with how forge (or chickenchunks) is loading the area. I'm just not sure when it started, though I don't recall any of this occurring in 1.6.4.