seedy

Hi James, I don’t know what URL the Blogger person is accessing, they are likely not savvy. Is there a way to PM or email the URL of the client site?

Hey Paul, good idea. I shouldn’t have bothered you without thinking of it. I opened the Plugins page for both sites and disabled plugins unique the troubled site one by one. I tried security or related ones first and found no winner.

Then I tried disabling Sell Media and login works again. I wasn’t actively relying on SM, just playin’, so it’s no loss at this time. If I do end up using it on another site I’ll know that I’ll need a different firewall. Or maybe the folks at https://graphpaperpress.com/ would be interested in the conflict if it’s reproducible.

Thanks for your patient help.

Thank you Paul, I looked into various directories on my shared account and came across error_log files, but many aren’t recently updated and the most recent had nothing pertaining. cPanel offers an error log panel, but it comes up blank.

IIRC, there was a way to make PHP report errors in the browser, like a verbose mode, but I’ve lost track of how to do that. Also, it happened right after the recent SSF update. The other site got updated the next day and didn’t have the same issue.

I imagine that this feature is a PITA to support, but given the amount of attempts on my login.php when it’s accessible under its own name, I think it’s a worthwhile feature and am grateful for it.

Thanks, Matt. I’ll have a look at the code.

It sounds more like an EIG problem than a WF problem. ??

That said, Matt’s suggestions were helpful and educational. Appreciate how WF supports and grows.

Thank you both for your patient and timely replies. All my sites are now disabled.

There are ironies here, but the best one is that I got emails confirming updates accomplished, but nothing whatsoever when one of them failed.

It can be caused by trying to upload a file that is too large for the memory allowed by your PHP install. Try a very small file and see if that works.

If it does, research “increasing PHP memory allocation”. You might need to either contact your server company or edit a text file to get it accomplished.

Hi, your NAS has a fixed IP, correct?
Did you have an account called “admin” on your WordPress site?
Did you update via the wordpress control panel, perhaps? Or does Synology offer an app installer and you used that?
Did you make any backups of the contents of the NAS as you worked?

Here’s where the questions are leading…a fixed IP makes you a steady target. Since you are beginning you may not have installed protective plugins.

Because WP defaults to an “admin” account when first installed it is the first thing tried my most scripters. The first thing I do with a new install is make a new admin account with an unusual name, log in with that, and delete the “admin” account.

Synology may or may not have support and/or auto-backup provisions that might recover a copy. I’m guessing that they also default to a given admin name and password for the NAS itself, did you change those? If not, it would be easy to break into your NAS and wreak havoc.

Also, it is just possible that you deleted or moved wp-config.php yourself. Or that, in making changes in the General section, you changed the location of the site. In the latter case, you’ll need to go into the db to change those entries. PHPMyAdmin is a tool that can help you do that.

Fixed the piwik.org issue, Apple’s default DNS, had recently reinstalled and piwik.org was the first thing that didn’t work. So much for supporting open source…

Uploaded latest version, all new. No styling on install welcome page and 403 when I advanced to next install step.

This goes beyond the NF scope of support, just for closure.

First, thank you for taking time to help. I tried both turning off the firewall and disabling the NF plugin. The Piwik login page on my server still lacks any stylesheet and I get a Litespeed 403 when I log in.

It looks like an attack might have done something to Piwik. I’d be happy to reinstall, but for some reason I can’t load piwik.org to get another copy. Even the wide-open idiot-mode browser Safari doesn’t go there.

It may be a Piwik issue, but I searched and found no one else complaining.

I tried the recommendations in the other thread and got the 403. Also tried the suggestion above and refreshed a few times. The 403 has Litespeed info on it.

Interestingly, the URL shows that I am logged in. The login page is missing any markup, it’s just two fields and a link to piwik.org that doesn’t work.

Tried it on less locked-down browsers and it’s the same. Not tremendously important, I don’t make money off the site, just trying to learn and so see each problem as an opportunity.

Also, in the spirit of trying to help, the error message in that panel could read…

<br /><br /><br /><br /><center><b>%%REM_ADDRESS%%</b>, your request will not be processed as received.<br />It was blocked and logged.<br /><br />%%NINJA_LOGO%%<br /><br />If you believe this is an unfair assessment of your good intentions, please contact the<br />webmaster and include the following incident ID:<br /><br />[ <b>#%%NUM_INCIDENT%%</b> ]</center>

Thank you for that great idea! Sorry for not thinking of it meself. I checked last two logs, no piwik mention. I’ll keep looking.

Had already gone through permissions with host.

If the sites essentially present the same thing to the viewer, put one domain on 301 redirect to the other.

Or… use PHPMyAdmin to slurp the .org data on occasion. That would be easyiest, use the Backup plugin to save the db every week and extract the numbers you want.

I can understand if the ideas are disappointing, but if you are concerned about separation between the non-profit and the .com, it might be wise to run them separately anyway, use a duplicated db with a different theme so no one can cay they weren’t aware of which site they were on.

Thank you Nik!

Perhaps identical copies of a test image with a different name to test limits?