I've running website on a Linux server. This server runs a lot of website, most of them CMS, mainly WordPress.
And sometimes something renames my files from wp-db.php to wp-db.php.suspected for example.
And my site are goes down.
Has anyone seen such thing before or has an idea what can causes it?
Thank you for your help in advance.
these files sometimes suspected by your hosting provider, or wordfence plugin also it could be to trick you to ignore the files
Related
I am conducting a test run of my concept control web panel project on Centos7 using LAMP. However, I am experiencing a bit of a problem. When I visit http://mywebsiteurl.com/users.db rather than say forbidden or display a blank page. The browser auto downloads the .db file. How can I prevent this from happening. Is there a way to restrict access to files with a particular extension?
Okay so after hours of research, trial and error. I somehow managed to fix my problem using the solution found here:
https://stackoverflow.com/a/5605110/18351396
I just changed the file extension to .db to suit my case.
Thanks everyone, especially CBroe.
Our wordpress installation just started to create a LOT of core files, each over 100MB and they have taken over my host.
What are they and how do I remove them?
Seems like your server crashes and the core files are saved.
I looked around for possible solutions and found more WordPress bloggers reporting this issue in the WordPress forums. I learnt that these are called Core Dump files and Wikipedia says core dump records the working memory of a computer program usually when the program crashes. Core dumps are often used to diagnose or debug errors in computer programs.
In these forums some people advised we can delete these files and save space after backing up all files and database. Some advise the core files can be read using GDB, the GNU Project debugger. I am not sure if I should delete these files and maybe you can help.
I understand that these files are hosted on our server to keep a record of useful data when the site crashed on a particular day, but I wonder if any hosting engineer is debugging this data or diagnosing why the server or unstable processes crashed or terminated.
http://www.quickonlinetips.com/archives/2009/03/wordpress-core-dump-files/
Your installation or server may be the issue. Check the error_log for more info.
Also may check http://www.complete-concrete-concise.com/web-tools/wordpress-generating-core-dumps.
I have two openx 2.8 servers running here. The issue is that trying to open the admin page redirects me to the full path www.myserver.com/www/admin/index.php with blank screen. Still I can access www.myserver.com/www/images/, delivery etc. I tried a lot of stuff without any success.
this one doesn't work for me OpenX Admin not accessible
I had something similar happen to me last week. Check your configuration file in the /var folder of your openx installation, probably called something like www.yoursite.com.conf.php. Mine was corrupted. I suspect outside malicious activity, especially since there are known vulnerabilities in OpenX.. I'm currently looking at upgrading to Revive Ad server, which is the successor and is supposed to offer a complete upgrade path.
Can you replace the /wp-admin directory of a Wordpress installation with another one without issues?
This question is very open, but my current context is that I'm transferring a Wordpress site from one server to another. I've just come to download the site via FTP, and the /wp-admin folder has disappeared. (I probably did something wrong, but I did not knowingly delete the folder). I have a development version of the site, and am wondering if it will cause problems to just use the /wp-admin from that.
Has anyone come up against a similar thing before, and does anybody know if this folder is generic?
You need to replace the folder with one of the same version. See http://codex.wordpress.org/WordPress_Versions
There are, of course, updates and bug fixes along the way in many, but not all, versions, and a copy of wp-admin of a version not the same as the rest of the install will break things.
Check the file version.php in wp-includes to find the version of your WordPress install. ( version.php is not in wp-admin). And file modification dates are not a reliable way to check versions.)
See https://wordpress.org/download/release-archive/ for all versions.
As long as no modifications to the core of WordPress have been done, you should be fine, but make sure that the wp-admin folder you're uploading belongs to the same WordPress version your website is running. You should face no issues at all.
Firstly, if you did have a Dreamweaver then try to search a word 'wp-admin' in Entire Website Folder in the search's Dreamweaver option.
Secondly, change all text that contain a word 'wp-admin'.
Third, change the folder's name.
Then test your wordpress, if there are errors so try to solve it or post a comment.
I have hired a programmer overseas to develop a Drupal website for me and he has done a very good job (the site is installed at his server). I payed him and he sent me the Drupal files and the database .sql file.
Here is what I have done so far:
1- I have created a database on my server named something different from the database file he has sent me and imported the .sql file with no problem. (naming the database as the one he has used during development is not possible for me)
2- I have uploaded the Drupal files to the root of my domain.
3- I have modified drupal/site/default/settings.php and put my database information there and I have modified the $base_url variable there.
The problem is that when I access the website I get a white screen and nothing else (even when I click on show source on my browser, it is empty).
I tried to do the same on a localhost on both Mac and Windows using MAMP and WAMP respectively, and I got the same result (empty screen)
anybody has any suggestion about what seems to be the problem?
Best Regards,
Its a PHP WSOD error most likely. Do you have a way to check crash logs?
Have you looked at The White Screen of Death? Typically when faced with this issue and unable to quickly find the cause I return to this handbook page to go through the possible causes. Unfortunately this is a common symptom of many different problems and can be difficult to pin down.
if anybody has the same issue. Problem has been solved by adding the following line to the PHP settings.php file:
ini_set('memory_limit', '64M');
Thank you all for the help.