Haven't received any blueprints in two weeks, can't access my filament

The CN you're getting (   CN=*.work-devl-vpn.us.e01.c01.johndeerecloud.com  )  says you're not actually talking to our servers. You could have a DNS override left over from some experiment you ran previously like editing your /etc/hosts file or you could have some sort of malware or maybe you just work for John Deere and you're running your work VPN and they're intercepting all your traffic. Can't say from the info given. Hope this is enough of a clue for you to either resolve the issue yourself or give us some additional clues to work with. Best of luck!

Thank you for your reply! I was able to resolve my problem by seetting my DNS IPv4 servers manually to Google's 8.8.8.8 and 8.8.4.4. Your insight was crucial, because I really don't undertnand much of this server stuff, but that was the right hint.

If you are interested, here's a story of why did this happen.

 

So, in my country (RU) many websites are blocked, though usualy it was bypassable by vpn. But from a while ago these blockings became serious due to enforced installation of new equipment with DPI technology capable of traffic inspection on the fly to most nodes of every provider. This became insurmountable by previous means. For example, we have youtube's and discrod's servers blocked. And to circumvent this firewall, some enthusiasts developed small tools that meddle with output traffic to make it encrypted against DPI. The two most popular pieces of software are goodbeydpi and zapret (if you want to learn more you can check these links: https://github.com/bol-van/zapret/blob/master/docs/readme.en.md, https://github.com/ValdikSS/GoodbyeDPI). I used both of them, and it was probably due to them that this situation occured. I don't know much how they do their things, but at least I can watch some youtube)

 

Thank you for your help  For now I can see my filaments, unravel old ones. Also I got daily drop in DST and can look through my item collection. I haven't recieved new drops in game yet, but I think the issue is resolved.

I'm glad you were able to resolve your issue!

Changed Status to Fixed