OK! Thanx for help to all and have a nice new year!

Only 2 more hints,but it works...

Can I clear the System logs?

Forum is running and login works!

But now the forum shows me in Admin Area that there are modified files:

Some of the source files for Invision Community have been modified.

• /www/htdocs/w00afc19/start/forum/applications/core/extensions/core/MemberFilter/Achievements.php
• /www/htdocs/w00afc19/start/forum/applications/core/extensions/core/MemberFilter/ProfileFields.php
• /www/htdocs/w00afc19/start/forum/system/Content/Content.php
• /www/htdocs/w00afc19/start/forum/system/Content/Item.php
• /www/htdocs/w00afc19/start/forum/system/Login/Handler/OAuth2/Custom.php
• /www/htdocs/w00afc19/start/forum/system/Login/Handler/OAuth2/Google.php
• /www/htdocs/w00afc19/start/forum/system/Member/Member.php
• /www/htdocs/w00afc19/start/forum/system/Text/Parser.php

You should download an unmodified copy of those files and upload them to your server. Once that is done, check if the problem persists.

Can I download the unmodified files without lost of information?

OK, found it! Now copy only the 8 folders inside complete to the server?

How to access the client area? I have always logged in through the admin section of the forum. This way is now unfortunately blocked...

Found it on the top!

But where is the full package???

1 minute ago, Jim M said:

I would suggest uploading a fresh set of files from your client area. That would indicate an out of date file or a modification in the file that is not compatible with PHP 8.

How do I do this and do the forum entries/users remain intact? Unfortunately I am not an IT specialist...

Last lines in errorlog from provider:

[27-Dec-2022 14:44:35 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259
[27-Dec-2022 14:45:06 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259
[27-Dec-2022 14:45:37 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259
[27-Dec-2022 14:46:07 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259
[27-Dec-2022 14:46:38 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259
[27-Dec-2022 14:47:09 UTC] PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/start/forum/admin/sources/base/ipsMember.php on line 259

I get 503

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later

Seems this is the end of the forum...

Now the forum is no longer accessible due to maintenance?

Are you trying to help?

Get an email that the validation mail to IPS cannot delivered... Have validate the account (button in email) and get another mail that can not delivered...

I have disabled pinsandparts now

Pinsandpart is an other website! oeffelke.de also!

Forum is in start/forum

Maybe these are fractals from very old versions? I use Invison Power from the beginnig as the software was for free...

this just came from the provider:

the entry in the -user.ini is correct. Therefore 512 MB are currently used. Currently the following message appears frequently in the log:

PHP Fatal error: Array and string offset access syntax with curly braces is no longer supported in /www/htdocs/w00afc19/pinsandparts/register.php on line 851

Tis is the answer fom the support of myhoster:

Quote

vielen Dank für Ihre Anfrage.

Laut Errorlogs reichen nun auch die 512 MB nicht (mehr) aus. Das deutet hier eher auf einen Fehler in einem Script hin. Haben Sie an Ihrem Forum kürzlich etwas geändert oder hinzu installiert?

Thank you for your request.

According to the error logs, the 512 MB are not (anymore) sufficient. This rather indicates an error in a script here. Have you changed or added anything to your forum recently?

        self::$lastError = new \ErrorException( $errstr, $errno, 0, $errfile, $errline );

This is line 992! What does this line tell me about the error?

He increased from 256MB to 512MB, but the log means it is not enough???

New entry in error log on server:

 Error dispatching request to : , referer: https://www.flippertreff.de/start/forum/index.php?app=core&module=system&controller=serviceworker&v=3aa3becd091672041690&type=front&loggedIn=false

the server-log is full of the following message:

PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /www/htdocs/w00afc19/start/forum/init.php on line 992', referer: https://www.flippertreff.de.....

For users who have logged in up to 11/24, I can access the profiles without any problems! Was there any update after 11/24 which could cause problems?

Users get HTTP: error 500 during  login

No, the change was made a while ago. Actually, I always install the updates when they are available. But I don't try all functions afterwards. Therefore I can't say since when the login error exists.

All 3rd party extensions have been removed. The last extension (deactivated until then) was "Auto Welcome". After I uninstalled it I only see a white page. No error message anymore, but also no user data... Slowly I am afraid to shoot down the forum completely...

This is the last mail from the support of the hoster:
Then the conversion to innodb should be done via PHPmyAdmin. Before you start your work, you should create a backup of the database, so that you can restore it to the current state in case of emergency.
Then a short tutorial on how to convert MyISAM to InnoDB.
Would that help?

I think this is the failure? But klicking on "fix this" will not solve the error...

Maybe the last update goes wrong? In November, all is OK with the forum...