MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

11/3/2017 7:16:33 PM
Gravatar
Total Posts 21

MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

I have a long-standing site running on MojoPortal v2.3.9.5 (MSSQL), hosted at GoDaddy on one of their (now) "Classic" hosting packages, and I'm attempting to upgrade everything to the newest version of MojoPortal (v2.6.0.0 as of this writing). The GoDaddy hosting is a Windows account (obviously) running IIS 7.0 and is configured for a .NET v4.0/4.5 application pool.

I duplicated my site locally to a Windows 10 Home Premium machine running IIS (v10.0.14393.0) and Microsoft SQL Server 2012 Express Edition.

After unzipping the MojoPortal v2.6.0.0 (MSSQL) package to a new folder, adding it as a virtual directory, converting that to an Integrated .NET v4.5 application, and pointing the web.config to the same database, the scripts ran perfectly without issue.

...so I'm good to go, right?

WRONG

I upload the files from the MojoPortal v2.6.0.0 (MSSQL) package, taking care to remove any files from the v2.3.9.5 installation, at which point I got a generic server error (500) with no details.

Just to see if it was the database, I set up a new, fresh MSSQL database and point the install to the new MSSQL. Browsing the site yields the same generic server error.

I also changed out the source files to match the MojoPortal v2.6.0.0 (MySQL) version, pointing it to a new, fresh MySQL database, and running the install yields the same generic server error.

 

All attempts seem to fail BEFORE running anything in the "\Setup" folder... as it never redirects to the "\Setup\Default.aspx" file. Browsing directly to that file also fails with the same generic server error.

 

It seems as though something in the basic functionality of MojoPortal is incompatible with the setup at GoDaddy... but I haven't been able to locate the issue. I've examined the trust settings, the folder write permissions, and the IIS and .NET versions.

 

Does anyone have any idea what's going wrong?

11/3/2017 9:31:26 PM
Gravatar
Total Posts 1992

Re: MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

Hi,

Thank you for your continued use of mojoPortal. 

I believe the problem you are running into is related to the version of .NET in use by your web server. I know it says it's running .NET 4.5 and it probably is. The problem is that mojoPortal 2.6 requires .NET 4.6.2 and hosting providers don't always list the .NET version properly because they generally show the CLR version which for .NET 4.6.2 and .NET 4.5 is just "4". 

You are able to run mojoPortal on your system at home because it has at least .NET 4.6.2 installed.

If you can get GoDaddy to upgrade your hosting or to install .NET 4.6.2 or higher on your current hosting, your site will run fine. If you can't get them to upgrade your hosting, you might want to check out our hosting packages

I hope this helps...

Thanks,
Joe

11/4/2017 3:37:28 AM
Gravatar
Total Posts 21

Re: MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

Might I make a suggestion, then?

Maybe STOP listing the CURRENT hosting requirements as "ASP.NET 3.5 SP1 or ASP.NET 4.0/4.5" on the MojoPortal website? ( https://www.mojoportal.com/hosting-requirements )

Just a thought.

I went there BEFORE ever downloading MojoPortal version 2.6.0.0 to check the requirements:

  • ASP.NET 3.5 SP1 or ASP.NET 4.0/4.5 — I have ASP.NET 4.0/4.5 — CHECK! — I can downgrade to v3.5 as well — DOUBLE CHECK!!!
  • IIS 6 or higher — I have IIS v7.0 — CHECK!
  • Database
    MSSQL 2005\2008\Azure — I have SQL Server version 2005 — CHECK!
    MySQL — I ALSO have MySQL — DOUBLE CHECK!!!

I seriously need a refresh of my website, and I'm really really trying to keep using MojoPortal, now that it seems to be "web 2.0" capable... but I'm beginning to see why THIS is the case! Had I decided to move entirely to WordPress, I could have manually re-created the website content and all uploads in less than half the time it's taken me (so far) to try to get MojoPortal v2.6.0.0 to work.

Sorry to vent, but why does upgrading MojoPortal always feel like pulling teeth? ...your OWN teeth? ...with a dull, rusty hatchet? ...and without any anesthetic?

11/4/2017 11:49:47 AM
Gravatar
Total Posts 1992

Re: MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

Hi,

I am very sorry for the confusion. We included a note in the release notice about the .NET 4.6.2 requirement but we failed to update the Hosting Requirements documentation. .NET 3.5 SP1 hasn't been supported in a very long time. We bought mojoPortal earlier this year and we have been working hard on updating documentation. Some of it is just very, very, old. We should have focused on the requirements documentation at the very beginning. Again, I'm sorry for the trouble this has caused you.

I've fixed that documentation now and I've added it to release checklist to be sure we don't make this mistake again. 

You'll note that the documentation now states that SQL 2008 and higher is supported. You will more than likely be able to use SQL 2005 for version 2.6.0.0 but I know that we are implementing some newer SQL methods for retrieving paged data that will require at least SQL 2008. 

Thank you,
Joe

11/4/2017 4:03:49 PM
Gravatar
Total Posts 21

Re: MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

I understand that mistakes happen and I appreciate your candor; however, that's a pretty gigantic thing to fall through the cracks.

As with the old adage "only a tiny percentage of people write to their congressman, so if you do it, you're actually representing thousands of people who have the same issue", the same is likely true here... namely HOW MANY people have tried to install MojoPortal, failed, and decided it was useless junk and went on to another CMS (likely WordPress) without ever bothering to register, sign in, and post a question to a platform they've never used before? (...and will probably never use because of their experience...)

I'm still right on the dull, rusty hatchet, though. smiley

 

BY THE WAY. I was able to crash your website because I use a browser plugin called "ScriptSafe" which blocks the loading of all client-side scripts until approved, and with that plugin running, submitting anything to the server (login, posting a comment or reply, etc.) results in an IIS error page. Client-side scripts should not be so powerful that without them your site bombs out.

The IIS error I receive is:

"Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster."

The scripts that cause the server error when blocked are: ajax.aspnetcdn.com/ajax/4.5/6/MsAjaxBundle.js and (most likely) ajax.aspnetcdn.com/ajax/4.5/6/WebFormsBundle.js.

11/4/2017 4:49:02 PM
Gravatar
Total Posts 1992

Re: MojoPortal v2.6.0.0 not working on GoDaddy classic hosting

Hi,

Again, I apologize for the oversight. You are right, it was a very big oversight. All I can do is apologize and fix the problem. I'm sure there were some people who had problems running mojoPortal 2.6 on old hosting and said nothing. I'm grateful you did let us know and again, I'm sorry we didn't fix the documentation. All of that said, the release notes were extremely clear that this version of mojoPortal must have .NET 4.6.2. The download page at GitHub even shows the requirement. 

Regarding the difficulty of upgrading mojoPortal; can you tell me, beyond the problem you have had this time, what makes upgrading mojoPortal so difficult? We're eager to make things better and easier but we need to know what to improve. Your ideas could help.

Regarding "crashing" this site. I do not wish to argue with you but you didn't "crash" the site. You caused an error to be thrown for your user session. The didn't fail for everyone using it, which is what I would consider "crashing" it.

Regarding the error you produced, mojoPortal is a WebForms solution (for now) and as such it uses ViewState. Usually, you would have received a nicer error message but we were in the middle of testing a new feature and had turned off CustomErrors so you got the big, ugly, in-your-face error message. The site doesn't completely "bomb out" without scripts but login does fail. I suspect that login will fail on a great many websites when scripts are disabled. I installed ScriptSafe and was able to browse this site very well. Since you keep referencing WordPress, I decided to check out wordpress.com with ScriptSafe enabled. I could not enter my login credentials at all, which I consider a better experience than getting an error message but it doesn't tell me why I can't enter anything, the form is just disabled. Also, a lot of the site just doesn't load. My point is that when users use tools like ScriptSafe they usually understand that sites aren't going to work 100% bug free. I would never expect any site to work completely when using a tool like ScriptSafe. I also wouldn't be alarmed by sites that give me ugly errors when I have ScriptSafe enabled.

I hope to help you get your site up and running with mojoPortal 2.6 and to make the upgrade process smoother in the future. As for documentation, we could use all of the help we can get. mojoPortal is a big project and it has been around a very long time. There is a lot of documentation that needs to be updated so if you wouldn't mind helping, please let us know.

Thanks,
Joe