Log in/Can't activate CMS 2 license!

@differentdan Can you tell me where to turn this off in cPanel?

I’m not 100% you have that in your cPanel, some web hosts have it, some do not. If you don’t see anything that says something like “Mod Security” or “mod_security” in your cPanel list of things then your web host probably doesn’t make it available..

I think that setting is disabled for me.

Ok, well the error code in your screenshot is an ISE 500 (internal server error) and since we don’t have any physical access to your server, that’s why we are suggesting you reach out to your web hosting provider and ask them, because they can check their server logs and see why it’s throwing that ISE 500 error. It could be many things going wrong and we are kind of shooting blind here..

With the above said if you want to jump on a Zoom call real quick I can try and see if I can troubleshoot this in real-time, with the limited access I have to your hosting environment. If you want to do that let me know and I’ll send you a Zoom link. :slightly_smiling_face:

@differentdan After a dialogue with my provider, I received this feedback. Does this tell you anything?


I am experiencing a “Network Error” when trying to log into CMS 2 in RapidWeaver Elements.

The website (https://kaffesystemer.no) loads and works normally, but the CMS login fails after previously working. I was able to install CMS 2 and edit content, but after logging out, I can no longer log in.

Browser console shows multiple errors:

  • Failed to load resource with status 401, 403, and 500
  • Connection refused to external API endpoint (api-eu.io)
  • CMS login displays “Network error. Please try again.”

This is hosted on Domene.no. No recent domain or DNS changes were made.

Could you help identify whether this is caused by API blocking, authentication issues, or server-side security restrictions?

No, becuase that looks like something you wrote to them, I don’t see anything that looks like a reply back from them. :neutral_face:

If that’s their reply, it looks AI generated too.

Does this server log tell you anything?


text/x-generic error_log ( ASCII text, with very long lines )
[21-May-2026 11:43:34 UTC] PHP Warning:  require_once(/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php): Failed to open stream: No such file or directory in /home/xmvugwkt/public_html/index.php on line 4
[21-May-2026 11:43:34 UTC] PHP Fatal error:  Uncaught Error: Failed opening required '/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php' (include_path='.:/opt/cpanel/ea-php84/root/usr/share/pear') in /home/xmvugwkt/public_html/index.php:4
Stack trace:
#0 {main}
  thrown in /home/xmvugwkt/public_html/index.php on line 4
[21-May-2026 11:43:34 UTC] PHP Warning:  require_once(/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php): Failed to open stream: No such file or directory in /home/xmvugwkt/public_html/index.php on line 4
[21-May-2026 11:43:34 UTC] PHP Fatal error:  Uncaught Error: Failed opening required '/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php' (include_path='.:/opt/cpanel/ea-php84/root/usr/share/pear') in /home/xmvugwkt/public_html/index.php:4
Stack trace:
#0 {main}
  thrown in /home/xmvugwkt/public_html/index.php on line 4
[21-May-2026 11:45:20 UTC] PHP Warning:  require_once(/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/composer/autoload_real.php): Failed to open stream: No such file or directory in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php on line 23
[21-May-2026 11:45:20 UTC] PHP Fatal error:  Uncaught Error: Failed opening required '/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/composer/autoload_real.php' (include_path='.:/opt/cpanel/ea-php84/root/usr/share/pear') in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php:23
Stack trace:
#0 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php(13): require_once()
#1 /home/xmvugwkt/public_html/index.php(4): require_once('/home/xmvugwkt/...')
#2 {main}
  thrown in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php on line 23
[21-May-2026 11:45:22 UTC] PHP Warning:  require_once(/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/composer/autoload_real.php): Failed to open stream: No such file or directory in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php on line 23
[21-May-2026 11:45:22 UTC] PHP Fatal error:  Uncaught Error: Failed opening required '/home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/composer/autoload_real.php' (include_path='.:/opt/cpanel/ea-php84/root/usr/share/pear') in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php:23
Stack trace:
#0 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms.php(13): require_once()
#1 /home/xmvugwkt/public_html/index.php(4): require_once('/home/xmvugwkt/...')
#2 {main}
  thrown in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/autoload.php on line 23
[21-May-2026 11:46:34 UTC] PHP Fatal error:  Uncaught Error: Class "League\CommonMark\Node\Inline\Text" not found in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/InlineParserEngine.php:118
Stack trace:
#0 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/InlineParserEngine.php(100): League\CommonMark\Parser\InlineParserEngine->addPlainText('Er du usikker p...', Object(League\CommonMark\Node\Block\Paragraph))
#1 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/Block/ParagraphParser.php(69): League\CommonMark\Parser\InlineParserEngine->parse('Er du usikker p...', Object(League\CommonMark\Node\Block\Paragraph))
#2 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/MarkdownParser.php(275): League\CommonMark\Parser\Block\ParagraphParser->parseInlines(Object(League\CommonMark\Parser\InlineParserEngine))
#3 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/MarkdownParser.php(106): League\CommonMark\Parser\MarkdownParser->processInlines(4533)
#4 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/MarkdownConverter.php(59): League\CommonMark\Parser\MarkdownParser->parse('---\r\ntitle: "Sv...')
#5 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms/Parser.php(32): League\CommonMark\MarkdownConverter->convert('---\r\ntitle: "Sv...')
#6 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms/Item.php(21): CMS\Parser::parse('cms/blogg/2021-...', Array)
#7 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms/Collection.php(23): CMS\Item::fromFile('cms/blogg/2021-...', Array)
#8 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms/CollectionBuilder.php(314): CMS\Collection::discover('cms/blogg', Array)
#9 /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/cms/CollectionBuilder.php(173): CMS\CollectionBuilder->executeQuery()
#10 /home/xmvugwkt/public_html/index.php(841): CMS\CollectionBuilder->get()
#11 {main}
  thrown in /home/xmvugwkt/public_html/rw/elements/com.elementsplatform.cms/api/vendor/league/commonmark/src/Parser/InlineParserEngine.php on line 118

That log makes it look like some of the files aren’t available :thinking: but this could be a different issue…

Did you contact your hosting company about this issue? If so, what did they say?

I have been in dialogue with them and they say the error does not lie with them and asked me to take this further with you :thinking:

Had a dialogue with Gemini and they came up with this answer.

Why does this happen, and how do you fix it? This almost always happens due to one of two things:

  1. An incomplete file upload: If you recently uploaded the files via FTP (e.g. FileZilla), the transfer may have been interrupted halfway, meaning not all files in the vendor folder were included.
  2. PHP upgrade: The log shows that your server is running PHP 8.4 (ea-php84). If your web host recently upgraded to PHP 8.4, the old CMS library may not be compatible, or fails during execution.

Solution:

  • If you are using Composer: Log in via SSH to your server, navigate to the folder /rw/elements/com.elementsplatform.cms/api/ and run the command: Bash
composer install

(This will download and reinstall all the missing and correct files).

  • If you are uploading manually (FTP): Delete the folder named vendor (inside .../api/) on the server, and re-upload it from your computer. Make sure your FTP program completes all file transfers without errors (there are often thousands of small files in that folder).

It’s just a guess, but try removing “Cookie-innstillinger” from the ECMS dashboard page. I can easily imagine that there might be a conflict there.

Did not fix the problem.

Hi @mrTablet,

This is a typical “not my problem” cheap hosting reply, and honestly, you deserve better. Compare the support they give you with what we do here, anyway…

We’ve been looking into this general issue of the Online CMS Editor not running on some web servers. The problem is, every server is configured differently so it’s pretty hard to build something that just works everywhere, especially on launch day!

However, we’re been working on some changes that should improve server compatibility, we hope to have that build out later today.

Once the update ships please try a “re-publish all files”. Fingers crossed this should resolve the issue for you.

I can’t login in either. I purchased the V2 CMS Studio. Placed the Online Editor within the dashboard directory and uploaded to my Host (Hostinger). It will not accept any inputs, like I am looking at an image. Also, I had added SecFilterEngine Off
SecFilterScanPOST Off to my .htaccess file.

@mrTablet, @skypilota72, @Pegasus

Please update to Elements 2.4.1 and see if that fixes your issue(s).

Be sure to use the “Re-publish All Files” option in the file menu.

Let me know how you get on.

Did not fix the problem.

That did it. Now to learn how to use this iteration, as my skill-set for CMS was EasyCMS (Joe Workman) within Classic.

HI @mrTablet I just managed to login successfully to your Online Editor install (using the credentials you emailed us yesterday) :smiley:

Maybe your browser had cached the page yesterday, or you’ve done a re-publish since your last post. Either way, it all seems to be working now, but do let me know if you’re still having issues.

P.S. Once thing I noticed is you’ve included additional components on the page, these components are causing styling issues in the Online Editor — the only component on the page should be the Online Editor. Nothing else!

I deleted config.php an hour ago and re-uploaded everything. Haven’t checked yet if everything is OK. Going to do that now :slight_smile: