WordPress is in the wrong folder on the server

I clicked on the link but unfortunately I do not understand any of the text highlighted in blue.

Any line preceded by # is a comment, and any line that does not begin with # is code. With comment lines removed, here is the edited version you would need:

# .htaccess for idc-canaryislands.com redirect to /wp/
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www.)?idc-canaryislands.com$
RewriteCond %{REQUEST_URI} !^/wp/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /wp/$1
RewriteCond %{HTTP_HOST} ^(www.)?idc-canaryislands.com$
## index.html for default
#RewriteRule ^(/)?$ wp/index.html [L]
## index.php for WordPress
RewriteRule ^(/)?$ wp/index.php [L]

When I open the .htaccess file it looks empty there is no text to change.
I did not create the .htaccess file someone else did it for me so I do not know what edits to make?

If someone just made an empty .htaccess file, all you would need to do for this part would be to copy the above into it and save it.

I have found the following link
https://codex.ww.wp.xz.cn/Giving_WordPress_Its_Own_Directory

I have never tried doing things that way because what I have suggested has been much simpler for me. You might or might not also need to later edit some additional links in your database, but you should (or at least might) be able to go to Dashboard > Settings > General and place http://www.idc-canaryislands.com in both boxes there and then put the above .htaccess in place and be finished.

edit: If you try the above precisely and more work is still needed, I will keep posting right here until you get it fixed.

Just to confirm the last part of your instructions, you said ¨put the above .htaccess in place¨, I have moved it into the WP folder which is within the public_html. The original .htaccess file is still in the original place.

No. This is what needs to be in /public/html/wp/.htaccess:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Or, just have nothing at all there and then *later* go to Dashboard > Settings > Permalinks and WordPress will write it. The .htaccess I had posted must *first* go in as /public_html/.htaccess to redirect ‘idc-canaryislands.com’ to its /wp/ sub-folder destination. To explain:

cPanel has your domain assigned to /public_html/ and you likely cannot change that. So, the custom htaccess in public_html will send your domain to /wp/ where WordPress will then be found and respond without ever even knowing it is in a sub-folder and your browser will only use ‘http://www.idc-canaryislands.com’ to get there.

There is a line of code your can temporarily place near the bottom of wp-config.php that I believe might fix that:

/**
* WordPress supports an automatic relocation method intended as quick assist
* for getting a site working after relocating it from one server to another.
* After the "define" statements and just before "That's all, stop editing!",
insert a new line, and type: /*toggle on/off*
define('RELOCATE',true);
/* Next Login as normal after being certain of the address being sent from your browser.
* Then look again in your browser's address bar to verify that you have logged in at the correct server.
* If this is the case, next go to Dashboard > Settings > General and verify the address settings and save them.
* Once the above has been completed, either remove the above 'define('RELOCATE',true);' line or
* comment it out with '//' or change the 'true' value to 'false'.
* Note: When the RELOCATE flag is set to 'true', the Site URL will be automatically
* updated to whatever path is being used to access the login screen. This will get the admin
* section up and running on the new URL, but it will not correct any other part of the setup.
* Those will still need to be altered manually.
/**
* That's all, stop editing! Happy blogging. */

To activate that single line, just add a slash after the /*toggle on/off* just above it so you will have this: /*toggle on/off*/ .

Before doing that, however, be certain tp clear your browser cache and then only go to this link: ‘http://www.idc-canaryislands.com/wp-admin/index.php’ . I have only ever used that code a couple of times, so I caution you to be careful with it since I do not know how it works.

The define('RELOCATE',true); line is the only line you actually need at all. The remainder of what I had posted is simply all the related commenting. Then after you have things straight, go back and either remove that line or else change it to define('RELOCATE',false); .

The /*toggle on/off*/ line is just something I use to turn the next line on or off as a comment by using just one character, and I apologize for not being more clear there.

Here is what you need:

define('WP_DEBUG', false);
define('RELOCATE',true);

/* That's all, stop editing! Happy blogging. */

note: Be certain to have your browser cache clear so it will hopefully not redirect you and then be sure to *not* include the /wp/ or whatever when you go to your login after adding that code.

note: If you have not already done so, you should now either remove ('RELOCATE',true); from wp-config or else change it to ('RELOCATE',false); .

Doing what you have done so far is part of eliminating possibilities (troubleshooting), and I do not know exactly what to suggest…

https://www.google.com/search?q=wp-admin+not+found+on+this+server

You are using /public_html/.htaccess to redirect your domain URL to /public_html/wp/, and then you have /public_html/wp/.htaccess for you actual WordPress installation. I doubt this will help, but you might try deleting the .htaccess in /public_html/wp/ to see whether that makes any difference. If it does, you should then be able to go to Dashboard > Settings > Permalinks where WordPress will write that .htaccess for you.

At this point, I would try looking in the database for some of the things ‘songdogtech’ mentions later in this thread:

https://ww.wp.xz.cn/support/topic/the-requested-url-login-was-not-found-on-this-server-1

And/or/also: Use phpMyAdmin to search you database for any instance of ‘idc-canaryislands.com/wp’ since that is part of both the old URL and the idc-canaryislands.com/wp-admin you now need to use. Just be careful about what you might do with any find/s you might make there…and be sure to have a fresh database backup alongside any previous one prior to making any changes.