Hi. I have a DNN instance with several portals. The main portal, 0, has a skin that was in use by us originally. As we made more portals, we switched to using a better looking skin. Both were designed by our in house webmaster. One day the webmaster quit, fairly unexpectedly. He left little to no documentation and we had nobody who knew DNN. I did PHP web coding as a hobby so I was shoved into the position as interim webmaster, just to keep things running until we hired a real one. Well, that was like two years ago lol. I figured out a lot as I went along, but I don't know how the system functions at its heart.
Today that became a problem because our site is very sick. Pages on portal 0 are fine, but any page using the newer skin template takes 3-4 minutes to load. It's not just an initial load, it's any load at all. I changed a slow loading portal to use the portal 0 skin and voila, loads fast. It has been working fine for years though. Yesterday everything was fine. I tried stopping w3svc and copying in portals\_default\skins from a backup taken a week ago when everything was good but to no avail. I rebooted the server, no change. The only thing out of the ordinary is that I see tons of errors in the system event log starting 12:30 PM yesterday like this:
"An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed."
"A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 1205."
I don't know if that is related or not, but I don't see why that would screw up one type of skin and not another. Being that I don't know how DNN works "under the hood" I don't know what to check to see what is wrong. I surmised that maybe some external website dependency in the skin was the problem so I tried opening Chrome's network console then loading a slow page. When done, the network output shown the initial document at 4 minutes but everything else was only milliseconds. So the long time was server side for DNN to prepare the page. While it wouldn't make sense to me because portal 0 works fine, I nonetheless installed SQL server locally and loaded the database and repointed web.config to it. Our regular SQL server is a separate machine, I wanted to be sure the latency wasn't coming from that but it made no difference. I've no clue what to check now and I'm at my wits end. Does anyone have any suggestions? Thanks!