This is very little to go on. Is there a url that we can see?

Our website is http://crawfordco.lib.mi.us/ and I apologize....I submitted just as I realized I hadn't included it. It made me wait before I could edit and add it. Thanks in advance for any help.

No worries, Karyn,
First thing: http://crawfordco.lib.mi.us/ is not really pointing to the website, so it seems. Because the website resides at http://crawfordco.lib.mi.us/DNN. It has the site in a frame (?)

Having said that; it just says an error occurred, so not very helpful. If you can turn the errors on (web.config) there might be some more information.

In your web.config file, set CustomErrors to Off. That should display more detailed error messages to EVERYONE visiting the site.

See: https://stackify.com/web-...ustomerrors-asp-net/

Better way (that not everyone sees the error, which could be an attacking vector if it's there for longer): set customErrors mode to "RemoteOnly" and start a browser with the web site on the server. This will give end users the custom error message and local users (on the server) the standard ASP.Net error page (aka yellow screen of death). Of course you can only do this if you have access to the server, at least with a Remote Desktop, KVM-Switch etc...

And please add a certificate to your site and enable HSTS. Read Why EVERY site should be secured by HTTPS. For more information download the presentation I did at DNN-Connect in 2019: DNN Connect Association DNN Platform Events > Events > 2019 > Sessions.

Happy DNNing!
Michael

Hello All,

First off thanks for helping with this issue: my name is Josh and I'm a tech working with Karyn to try and get this fixed. Looking at the web.config file it seems the customErrors mode was set to RemoteOnly, but when I started a local browser session I was seeing the same screen as before with no additional information. Here are a couple other things I've looked into so far, maybe you all can let me know if I'm on the right path or not:

I found this forum: DotNetNuke Error "An error has occurred" "An error has occurred" after moving site from Localhost to Production site - DNN Creative Magazine for DotNetNuke - DotNetNuke Forum, DNN Creative Magazine, Video Tutorials, Skins, Module Reviews - DotNetNuke® - DotNetNuke® Questions and the gentleman helping seemed to recommend 1. checking the connection strings and 2. checking skin files. I can copy the connection strings here to make sure everything is correct, and I'm not really sure how to check on the skin files.

I tried viewing the dbo.EventLog table, but for some reason it seems that it stopped logging some point in the past and I have no recent relevant information from there. I do have the IIS logs but I'm not sure how helpful they'd be.

This page: DNN showing ‘An error has occurred’ - Let’s fix it (bobcares.com) recommends looking at the dbo.PortalAlias table and removing null values if they're there: I can see a whole row of null values but I can't seem to delete them, and I'm not sure if they're there by design.

I know this is a lot, and I'm trying to go in several different directions since I don't have much to go off of so far, so thank you for your understanding and all of your help.

 

 

No, your table should look something like this.

Btw, DNNSummit just started so, most of us currently live in/on Slack. The community channel (formerly known as open help) is on
https://join.slack.com/t/...IAChDA3BxIVRsRs3fCDA