M-Files Web stopped working

Our M-Files web server did its auto-update to 22.9.  After a time, we get 404 and 500 errors; also certificate errors.  When we try to browse it from outside, we get a certificate warning, then a "You do not have permission to view this directory or page" error.  What's going on?

  • Is your SSL certificate possibly exired? 

    Does your .Net framework at server meet the requirements mentioned at the user guide? 

    Is your IIS runnign on same machine than M-Files, or on separate server? If it is running on separate server, please make sure the IIS server has the updated M-Files version and .Net framework as well. 

  • We run M-Files Web separately from M-Files application server.  Both are at Version  We just updated the .NET framework from 4.6 to 4.8.  That got some of our functionality back, in particular, the REST API connection.
    Our certificate, issued by GoDaddy, is valid until November.  but when we try to run M-Files Web, we're still seeing a different certificate pop up:
    This is not part of our machine's list of certificates.  Did the update come with its own certificate designation?  Just grasping at straws here.
  • We can get around this problem by clicking Cancel when the certificate pops up.  When we do that, M-Files Web login appears.  Still, I would like to know where this certificate came from.

Reply Children
No Data