abletec

Hello, Nathan12. You would need to go to your hosting provider’s control panel & see if they’ll allow you to change the version of PHP. Otherwise, you’ll need to contact them & ask if they’ll do it for you.

Hello, nathan12, & welcome.

What I generally do in a situation like this is to install WordPress to a separate folder on the site. You didn’t provide a link, which actually in this case would’ve helped, at least a little. Generally hosting providers give clients at least 1 script installer by means of which they can install scripts like WordPress. I’ve worked w/a client or 2 on Bluehost, but I really can’t recall offhand which 1click installers they provide. If available, I like Softaculous, simply because I find their scripts to be up-to-date, which I’ve not always found on other similar installers.

These installers give you the choice of installing either to a separate folder or to the web root, the latter is done by not filling in a directory name. That will, however, overwrite the existing site, so please fill in a directory name when the installer asks for 1.

Your next task will be to choose a theme. You can use 1 of the provided default themes, or, conversely, go to http://www.ww.wp.xz.cn/themes , where you can search on a staggering number of keywords to find themes that match your preferences.

Once ready to make the site go live, please consult the following article:

Giving WordPress Its Own Directory

Because I’m not sure how this site is built–I have a severe visual impairment & the posted images, unfortunately, were not readable for me–it’s hard for me to instruct you how to import the site’s content. If you’d like to provide a link, I may be able to assist you w/that as well.

Good luck w/this. The learning curve can feel a bit steep at first, but it’s not like you have no technical background whatever, & those folks do learn this stuff.

I had no problem viewing your image, Ustus. Since this is a Russian website, then obviously I wasn’t in too good a shape reading it, as, unfortunately, I don’t understand Russian.

1 thing I like to put in my configuration is the following:
# The following applies to static files: images, CSS, javascript
location ~* ^.+\.(jpg|jpeg|png|gif|ico|css|js)$ {
access_log off; # Disable logging
# Allow client browsers to cache files for a long period of time
expires max;
}

I also look at files being included very carefully. I like to change things in the .conf files such that only files w/a *.conf extension are included. I rename other files in directories being included so that stuff isn’t accidentally included that I don’t want. That can eliminate a lot of troubleshooting.

Please let us know if you’re still having trouble.

Hello, johnjullies, & welcome.

Unless you have parked this domain, then it would appear your site has in fact been compromised.

when fixing a hacked site, there are really 2 objectives. The first is to remove the evidence of the hack, which is what most site owners concentrate on. The 2nd is to make sure the bad guys can’t gain entrance again, which is actually as or more important than the first 1, as all your hard work of fixing the site will be demolished in a matter of seconds if the criminals get in & hack the site again.

The first thing you should do is notify your hosting provider. They may help you, they may not, but sometimes the hcompromise can be of an entire server rather than a single site, and, if that’s the case, then they need to take action.

Second, make certain any device you use to log into your site is clean of any malware. You may need to do more than 1 scan using different scanners, since no scanner can catch everything.

Make certain also that your network is secure. Change the default username/password on your router, do not log into your site using a public hotspot, & use a secure file transfer protocol rather than just plain FTP.

These precautions are all so that your user credentials don’t fall into the wrong hands.

Now–please change your hosting control panel password, your WordPress dashboard password, & your database password. Don’t forget to paste that into your wp-config.php file. Also, change your salt keys as per the instructions in wp-config.php to log out all users. Please make the passwords long, containing upper & lowercase letters, numbers, & punctuation.

Next, take a backup of your website’s files. Be certain to label it such that the label contains both the date you backed it up on, as well as the word “hacked”–we certainly don’t want you accidentally restoring this backup! This can be helpful, though, in terms of perhaps being able to determine how this occurred, though my feeling is that it likely did so because of an outdated site. Probably you should just back up your web root. Depending on your host, it might be called public_html, htdocs, www, or /. If you don’t wish to back up the entire root, then at least back up your uploads folder, as well as others that might contain content that can’t be replaced.

Please also back up your database as well. The article at
http://codex.ww.wp.xz.cn/Backing_Up_Your_Database
shows you how to do that, in case you need it. The section regarding phpMyadmin is likely the most relevant to your case. It’s going to be necessary to search that database file to see if any evidence of the hack exists there. That can be done by opening the file in a text editor. To start off with, consider searching for the words:

<script
<? php;
base64;
eval 

preg_replace
strrev

You might also wish at this point to backup your WordPress content. To do that:
* Log into your WordPress dashboard.
* Go to ‘Tools > Export’.
* Choose to export all content.

WP-CLI can also be used if the script times out & if you have shell access.

While in your dashboard, go to ‘Users > All Users’ and delete any users there that you don’t recognize, especially administrators. A WordPress account should never contain the username ‘admin’. If yours does, make an administrative account that does not contain the word (don’t forget to use a very strong password), then delete the old admin username account.

Also be advised that sometimes supposed image files can contain code, so open all your image files, particularly in your uploads folders, to ensure they really are images & don’t contain code. Better yet, if you have the images on your machine, replace files in the uploads folders with them.

You might also wish to consider installing Wordfence. Check the options to scan files outside of WordPress, for administrative accounts not made by WordPress, & scan uploads as executable. These options can be turned off later, but right now they can be invaluable in terms of finding hacked files.

If you find nothing, either in your database or in your /uploads folders, then the next step is to delete, then completely reinstall WordPress, as well as any plugins or themes you were using. I also advise creating an entirely new database w/a new user & password. You can then import your content into the newly reinstalled site.

If your site runs on the Apache webserver, please also let someone knowledgeable look at your .htaccess file so they can make certain no backdoor code exists there.

Please let us know if you require additional assistance.

Hello, mogibb63, & welcome. There’s a lot you don’t tell us. Specifically:
* What version of WordPress are you running?
* What kind of hosting do you have–shared, VPS, or dedicated server?
* The error message you receive, if any.
* Whether you’re hosting on Windows or Linux.
* What is your webserver–Apache, Nginx, or other?

You might try deactivating all plugins, switching *temporarily* to a default theme (they begin w/the word ‘twenty’), install & run the Health Check & Troubleshooting plugin (https://ww.wp.xz.cn/plugins/health-check/) & see if it flags anything.

You might also try the update at this point & see if it works–if yes, then it points to a plugin or theme conflict–if no, then file permissions/ownership is a more likely cause.

The answers to the above questions would definitely help us help you.

Hello jperson19468, & welcome. Could you please let us have a look at your .htaccess file? Please let us know if you need instructins on how to do that. Please enclose code like:

line 1
line 2
line 3

When going to the site w/o the /wp, it throws a database error. So what, if anything, are you running on just the .com site? & if it’s a content management system like WordPress, did you install the /wp site into the same database?

Just trying to figure out the structure here.