After trying to put the forum into maintenance mode, it “disappeared”

After trying to put the forum into maintenance mode, it “disappeared” Started by Mrs. Chaos · June 09, 2026, 11:50:29 pm · Read 715 times 0 Members and 2 Guests are viewing this topic.

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #15 – June 14, 2026, 11:58:05 pm

Thanks for your replies, and sorry for the delay in getting back to you. I haven't had much time to attend to the forum lately. I won't be able to try out your suggestions and instructions for another few hours, but hopefully, I'll manage to bring the forum back to life in the process.
No matter how it turns out, I’ll definitely get back to you afterwards.

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #16 – June 15, 2026, 02:25:56 pm

Yes, I can go to "elkarte_log_errors", but it’s empty and doesn’t show any errors.

There’s other content on the server, but the forum is the only thing that’s inaccessible or not visible. Everything else works or is displayed.

In the meantime, I tried again to simply restore an old backup of the forum, but that didn’t work either.

Should I just create a new database? Could I then simply import the backup from about a week ago into it and just swap the old database name for the new one in the settings?

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #17 – June 15, 2026, 05:50:54 pm

I don't feel it would be the db as you are not seeing any errors in that log. That means it not making it very far.

You can try running repair settings to see if it finds anything.

Since its not logging errors in the ElkArte DB, the real failure reason will be in the server logs ... either in your PHP log or in your web server error/access logs.

Did you version of PHP change during any of this? I can't remember what version 1.1.8 is compatible with.

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #18 – June 18, 2026, 08:23:24 pm

Quote from: ahrasis – June 14, 2026, 03:38:36 pm
What is your problem @Steeley in attacking me? ....

Hi Arasis, (This is Steeley, posting as "snuffy")

I had no intent to attack you. If I wanted to attack you I would have questioned your parentage or something about your personality, intelligence or physical appearance, not your troubleshooting advice.

No, I was trying to tell you your suggestion "wasn't the best approach" to the problem. And I had a good reason..
Yes, if it works, great.
But if it doesn't, as I tried to explain, now you've got another puzzle, because you've introduced another element (or two) that you do not know doesn't have its own issues, separate from the one you were originally working..

How do I know this?

Because I did exactly what you suggested just the day before I saw your post and generated a whole lot of new work for me I wasn't counting on..

Permit me to explain. My host had this nasty habit of "updating" the servers, without notification. Only clue was when I discovered some aspect of the site no longer worked properly - email stopped going out, attachments disappeared, etc.. and to boot, they upped the cost dramatically.. I decided it was time to move. (The site wasn't broke, but now was trying to make me broke.. regardless, the solution is to copy my site to another server).

And so that weekend I was in the process of moving 4 websites to a new host's server.
The website that hosts my ElkArte platform had several issues after I copied it over to the new server.. nothing to do with ElkArte, it turned out, it was more fundamental .. after hours of troubleshooting getting nowhere, I contacted my new host and asked about the problems I was having.

Turned out there were two issues:
1 - php scripts no longer run in the cgi-bin directory (fine on my old server??)
2 - the directory privacy issue (.htaccess / passwd files) will not function properly until the nameservers are pointed at the new server. (Until I knew that, there was no way I was going to change nameservers and go live with "private" sections of the server open to the world).

So, the new site was, well, not broke, actually, but not working as expected - and it was the result of doing exactly the same thing you had recommended Ms. Chaos do - (for a different reason, but still) ..create a copy and see if it works...

Again - that's great .. if it works. If not, you end up spending hours chasing the NEW problems that had nothing to do with the original task you were trying to do. Just like I did..

But wait, there's more! To make matters more frustrating, the domain registrar for one of my domains went down! AS I kept trying to access them, I got to watch their efforts over the day as the various error messages I was getting trying to log in gave me clues as to their progress restoring their site.. frustrating because I absolutely had to have the site operational by last Tuesday or the domain on the old server turns into a pumpkin and my userbase is out in the weeds.

And of course there's tons of email accounts I had to migrate using ip addresses for both the old and new servers since I don't know when over the following 24 hours after the nameservers are updated that the dns changes are going to take place, and every account needs old and new credentials and ip addys for each and every account entered into my migration tool. And if an error (I got several with several accounts), have to trouble-shoot that too (inevitably it's a typo on my part).

So, I'm bouncing back and forth between three servers (old one, new one, and the email migration) and two computers, two steps forward and one step back, and, oh, yea, Ms Chaos and her issue..

If I sounded a bit terse in my post, sorry - it wasn't you.. I was trying to keep from throwing my desktop computers out the window..and didn't want Ms Chaos following me down a rabbit hole if she tried what you suggested and that activity didn't work for her either.

Now here's the kicker..

I decided not to migrate the forum. My user base is all in their 70's, 80's or fertilizing the grass above them now, and nobody has logged into the forum in over a year. No point getting ElkArte working again behind my "protected directories" on the new server if nobody is going to use it anyway (never mind I couldn't get the protected directories working either). So I've now archived about 10GB of discussion (read only) and it will all go to a national military library for posterity when I finally close the site down entirely.

So, from a practical personal support aspect, I have no reason to maintain access to this community.

Yet, I was planning to "stick around" and, if able, be helpful to others on occasion.

Except, I log in, and see that I am "banned"! Only explanation is "Attacking Moderator"?

Being "banned" over a misunderstanding really isn't the way I want to exit and be remembered. I've gotten a lot of help and knowledge from y'all and perhaps a bit of friendship. I've certainly never had any ill feelings or hostility toward you. No reason to burn those bridges, especially over a misunderstanding.

But if I'm no longer welcome.. hey, it's no skin off my nose.

But, before I post this, just a "pro-moderator tip" based on almost 30 years of group moderating - I'll post it in the open since it might help others with less experience moderating discussion forums:

Once the ban flag is set, the user can't access or read anything written, so it is a waste of time to post messages to the user asking or explaining anything before you pull the trigger. If you expect a user-view or response (or don't want to piss someone off over a misunderstanding), don't set the flag without giving the user a chance to see, and maybe address the issue.
I have no idea who has moderator privileges any more here, so seeing a message saying I "attacked the moderator" left me headscratching.
Did someone hack in on my account and flame a moderator? Was this a mistake? Someone a bit "thin skinned"?
"No clue" is a hell of a way to walk away..

If you're the "moderator" who set the flag (or if not, whomever is), feel free to delete this account as I won't need it any more if the ban flag is lifted. If it's the desire delete the Steeley account too, then no point to continuing the conversation..

Semper Fi..

Steeley (as "snuffy)

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #19 – June 22, 2026, 03:51:26 pm

Quote from: "Spuds" – June 15, 2026, 05:50:54 pmYou can try running repair settings to see if it finds anything.
Did you version of PHP change during any of this? I can't remember what version 1.1.8 is compatible with.

Sorry again for the late reply. Unfortunately, I haven’t had time over the last couple of days to keep on top of my forum.

I wasn’t able to get the repair settings to run, unfortunately; it just wouldn’t work.
The PHP version has been 8.1 for quite some time now, and I haven’t tried to change it.

I’ve been experimenting some more today, but nothing has led to a positive result.
Now I’m wondering whether I should perhaps just install a completely new forum – one that’s up to date and fully current.
I’m just not sure whether I’ll be able to reinstall at least most of the add-ons I’ve used so far, so that they’ll still work afterwards, as some of them were created or last updated quite a while ago.
Would it at least be possible to import my backup from 1 June into a new forum? Would I have to create all the categories myself first, or would they be created automatically when the backup is imported?

My hosting provider offers the following:
MariaDB: 10.11.14
PHP versions: 5.6, 7.4, 8.1, 8.2, 8.3, 8.4, 8.5

Which PHP version should I choose for a new/up-to-date forum?

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #20 – June 22, 2026, 06:56:00 pm

Hi Mrs Chaos,

First, php 7.2 will definitely work, probably 5.6 as well. But if 8.x was working then the version shouldn't be an issue either..

May I suggest something really simple and basic.. just a 'reality check'

Find the directory on your server that contains your forum "index.php" file

Rename the file "Forum-index.php"

Now in a text editor, copy the following:

Code: [Select]

<!DOCTYPE html>
<html>
    <head>
        <title>PHP Test</title>
    </head>
    <body>
        <?php echo '<p>Hello World</p>'; ?>
    </body>
</html>

Save the file as "index.php" in that directory..

Now, with your browser click on the HTML link that launches your forum..

You should get a display that says "Hello World!"

Let us know what you get.

If you get an error.. stop worrying about ElkArte and let us now find out what's screwy with the server ..

If, as I expect, you get "Hello World" displayed, then php is functioning on the server and from that directory.

Then you can delete the new index.php file and rename the "Forum-index.php" back to "index.php"

And next, maybe @Spuds can suggest some temporary edits to the forum index.php (or perhaps some other php file) to eliminate checks and cut straight to a streamlined/basic launch of the forum, without added/custom themes, addons, etc.. and see if you get SOMETHING besides whatever error (or nothing) that you're getting now.

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #21 – June 23, 2026, 09:19:02 am

I followed your instructions and afterwards a page displaying ‘Hello World!’ appeared.
And now I’m going to delete the new index.php file and rename ‘Forum-index.php’ back to ‘index.php’.

Re: After trying to put the forum into maintenance mode, it “disappeared”

Reply #22 – June 23, 2026, 09:42:32 pm

OK, unless @Spuds comes up with a better idea for troubleshooting the existing configuration, what I would do, now that we know the server appears to be functioning to "minimum requirements" that should support ElkArte, is to back up your entire current server and tuck it away on a really big local drive. I'd use FileZilla or something similar, to get your entire server file structure copied down. Be patient, it will take awhile.. Pay attention to any corrupted file errors during transfer - them are potential clues!
Once copied down, set the properties on the copy to "read only".
Also, back up the database(s) locally - usually your server tools has that ability. Make sure you have the June 1 Forum backup (last assumed-good copy) backed up locally too.

Then I would delete the ElkArte directories on the server entirely.

Next, I'd set my file manager on the server to show hidden directories (if not already) and scan through the server file structures. You'll probably see some hidden directories that replicate the file structure of the "unhidden" directories. Delete any files that are in hidden directories named the same as the ElkArte directories. (FileZilla shows the "hidden directories" auto-magically. BTW).

(you might see something like ".hiddensomething/public_html/myforum/goodstuff/... with a file something like "fubar.xyz" or whatever. Delete the file.) Be especially suspicious of files created or modified on the date/time you were attempting to deal with the suspected DoS attack.

You're trying to find and remove any latent 'klingons' spawned and hiding on the server.

Now restore your June 1 backup. and cross your fingers. (I assume the backup includes the database...)

Tell us what happened

If it works, you may not be out of the woods yet, but at least you've got something to work with.
(Work with it until you have the server working correctly, then remove the read-only flag on your local copy,, and delete it!)

And now build another local copy of the now "properly working" server using FileZilla, back up and download the database(s), and tuck them all away safely.

Pro-Tip: Get a directory/file comparison tool.. Later, if something goes awry, you can see what has changed from your last known "good server copy" on your currently malfunctioning one!

But if still no joy, the June 1 backup still doesn't work, you'll have to decide what to do now.

Remember, you have a complete server backup locally..

(First thing is to ask your host what you need to avoid doing if you want to preserve existing email accounts .. more on that in a bit..)

Your options include:

Ask your host to wipe your structure (*), and then restore ONLY the currently working HTML parts of the directory structure from your "FileZilla" backup, and then install the latest ElkArte package and configure it from scratch. Or...

Ask your host to wipe your structure, and then restore the entire server from the FileZilla backup, included the database backup, then try to install v.1.1.9 over it and pray.
(Note, you could try this now, after you've copied the server down locally as above, but if it doesn't work after the "upgrade" - and my bet is it won't - delete the forum structure from the server and the database and copy back the deleted directories and files from the backup copy using FileZilla, and the database from the locally-stored backup, and then go to the beginning of this post and follow it.). Or..

Ask your host to wipe your structure, and then restore the entire server from the FileZilla backup, and also include the database backup, and continue troubleshooting.. Again, pay attention to any corrupted file errors during transfer.

(* "Wipe the structure = host will probably just delete the domain entirely, and then recreate it fresh, Ask if the current email accounts on the mail server will remain so when you copy the file structure back the account support files in your directory are already there, along with the passwords. If that isn't possible (if you delete the server or wipe it, the mail accounts vanish too?), and you have a lot of email accounts with stored messages in them, then don't wipe the server, just delete everything except the structure from the root directory relating to the mail accounts to keep the mail server from wiping out the accounts when the mail file structure disappears. Discuss this approach with your host for validity..)

Or, just wait until @Spuds provides a better idea..