Seeking for knowledge
Yeah, I didn't find strange it reverted to using the old config, what seems strange is that it is not even working on a firmware version it used to work with and with a config that used to work as well.
Really thought the downgrade would have made it work again.
What's really strange is that with the downgrade, it even returned to the original configuration the one that was properly working before and still nothing.
Downgraded to 1.10.5 and still can't establish a proper connection or get any other type of log.
Version: v1.10.5
Build ID: 5098915
Build on: 06/22/18 13:55
Copyright: 2012-2018 Ubiquiti Networks, Inc.
HW model: EdgeRouter Lite 3-Port
HW S/N: 788A2041AA25
Uptime: 01:19:49 up 1 day, 4:46, 1 user, load average: 0.23, 0.16, 0.14
Could this mean the device is having some sort of problem or could it be Internet Service Provider caused????
@scottalanmiller The most login prompts are using it in Chrome.
Chrome has a bug regarding the websockets protocol and NTLM authentication. This effects the following tools: Events, PowerShell, Remote Desktop.
https://bugs.chromium.org/p/chromium/issues/detail?id=423609
@pete-s Those where taken using chrome but all browsers have the tools.
Here are couple screenshots from firefox webdev tools
Performance Tab
From the google chrome dev tools you can even get an audit using Lighthouse
You get a report like this:
For starters use the dev tools of your browser:
Here is the performance profile from mangolassi on my computer
Network performance of the assets, as you can see many things are already cached on my disk.
About 640 days of uptime on the server, so that could be a reason.
@taurex Site to site is working properly
@taurex just added the ipsec-interfaces setting even though it is deprecated according to the documentation and still nothing 