Yes. DNN Platform is a free, open-source CMS under the MIT License.

What is the tech stack for DNN?

DNN runs on ASP.NET (.NET Framework 4.8+) with Microsoft SQL Server (2017+ or Azure SQL).

DNN Platform is community-led and a member project of the .NET Foundation.

What’s the difference between DNN and Evoq?

DNN Platform is the open-source core that's been wildly popular and adopted for over 20 years. Evoq is a commercial offering maintained by DNN Software (IgniteTech) that builds on DNN.

DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

DNN axd files error mime type or Error 403

0 Replies

0 Subscribed to this topic

28 Subscribed to this forum

Sort:

Author

Messages

Moore Creative

Growing Member

Posts: 41

MVP

4/18/2021 1:14 PM

We recently encountered an issue where moving from one server to another of the same DNN instance had the newer server having problems with the axd files where they displayed either a mime type or 403 error.

I went searching for similar issues and ran across two of the older DNN forum with similar questions/issues:
https://www.dnnsoftware.c...tps-permission-issue

Their original question/issue was listed as:

Hey,

i´m running DNN version 07.02.02 and have my site configured to use HTTP and HTTPS.

I use the HTTPS for externel login and HTTP for internal login.

But when i login via HTTPS i always recieve this error:

Failed to load resource: https://website/Telerik.W...a9e03bb1b%3aa19c4d24

server responded with a status of 403 (Forbidden)

The strange thing is that the app pool user has 'full control' file permission on the DNN folder and still recieves a forbidden error message...

I hope you can help me

Thanks

In a recent encounter with the same type of issue, different browsers were giving different error responses for the webresource.axd and the Telerik.Web.UI.WebResource.axd files... one was simply giving an Error 403 denied type of response, others were suggesting mime type issue.

In the end, in this occassion, it turned out to be Web Application Firewall rules within Plesk that were causing a problem. The old server had one set of WAF rules, the new server had newer/different Plesk WAF rules and once adjusted, the site ran correctly.

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy.
No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved