In the NXFilter log I see a lot of errorsĮRROR - LoginListener._dealLogin, Couldn't find the user 172.16.19.123, d41d8cd98f00b204e9800998ecf8427e, agentName = CxLogon-win.Īny idea what's causing the website has been blocked error? I have to stop my Azure migration for now. When you enable authentication, NxFilter forwards any unauthenticated user to its login page unless they have IP address associations. The AD and Azure instances of NXFilter have similar settings and I have never got this error with AD users. If it is blocked without a reason it might be from your browser cache'. They will receive an error 'website has been blocked'. Every now and again a user will receive an error when visiting a website that they have visited successfully in the recent past. All desktops use Chrome with the CXForward extension installed. CX Logon is configured to auto register new users and add them to a default group. The first DNS of the desktop points to the NXFilter Master and the second DNS points to the NXFilter Slave. You can run NxCloud on your cloud server and you can run NxRelay in each office. My desktops are Windows 10 Pro joined to Microsoft Azure with CXLogon v1.0.5 installed. 2 08-20-2021, 08:15 AM I don't know what exactly you want but if it's about dealing with multiple offices having their own Active Directory from cloud based filtering, you can go with NxCloud + NxRelay. I have installed another instance of NXFilter for use by the Azure users. LetsEncrypt mandates a 3 Month rotation with new certs, new SSL base for encryption.I'm migrating from Active Directory to Azure.(At least you’ll likely be blissfully ignorant your server has long been rooted…) A self created ssl cert is usually static for eternity. ![]() (Gives a potential hacker a years time to use brute force)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |