Self-hosted blog admin login redirects to www.remarpro.com

It’s not your personal reputation that was questioned. It’s the whole concept of encouraging people to pass sensitive server access info onto a stranger on a forum that is the issue. Would you give your house keys to someone you only met in the street 5 minutes ago?

@esmi – Firstly, I wasn’t encouraging them to post any details publicly. I thought that would be pretty clear ??

Again, I do understand that this should’t be encouraged etc. However, I think it can be silly to spend 3 hours trying to explain how htaccess etc works when someone who is familiar with wordpress can sort this problem in under two minutes.

This is becoming more and more of an issue for peeps who upgraded.

There needs to be instructions posted on a sticky….and given to ISP hosts.

– birdie

wasn’t encouraging them to post any details publicly.

I agree. And if I implied that, I apologise unreservedly.

someone who is familiar with wordpress can sort this problem in under two minutes

But that rests in a huge assumption – that this person can be trusted. Unfortunately not every poster to this forum can be. ??

@esmi – I totally agree. I don’t like giving out my login details either unless it’s a plugin or theme developer I have been working with. ??

@megs1383 – if there is no htaccess file there, the quickest thing to resolve this would be to create a blank file and save it as .htaccess. Alternatively, create this in your file manager via your host. The file should be placed in the root of your WordPress installation.

Then go to https://meganbastian.com/wordpress/wp-admin/options-permalink.php and set the permalinks (you may have to change the permissions of the file to 755 or 777 temporarily to do this).

On a site note, have you not thought about using the name blog instead of wordpress i.e. https://meganbastian.com/blog/

@birdie breeze: Actually, if you look at the larger picture, it’s not a common issue at all. There are only 2 people with the problem, in this topic and I’ve not seen it anywhere else. So that strongly suggests that it’s server and/or site specific. Which isn’t quite the same as saying that it applies to the hosts in general. In your particular case, I think your hosts’ support may have done more damage than good and that it might be better if any further discussion continued within your own topic. Your situation is quite different to the original poster’s

@megs1383: Have you tried:

– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

– switching to the Twenty Eleven theme to rule out any theme-specific problems.

– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress.

On a site issue, I wouldn’t advise anyone tampering with the contents of the .htaccess file unless you know exactly how it works. It controls how urls are generated (amongst other things) so you shouldn’t change anything unless you know how to change things back should things go wrong.

Oh, I have been rooting around, and another person posted a new thread a few hours ago….they just have different subject headings. Different Topic/Thread – same exact issue. Everyone is chasing their own tails.

On my site, everything has been done, except not sure if they re-upped the wp-admin and wp-includes folders – BUT, they did tell me they checked them all and they were sound. I’ll try the re-upload of them. I did the plug-in’s trick, and Twenty Eleven was switched in. Which, I want out and my GPP as soon as this is fixed. Clearly the techs had gotten the same info you supplied.

@birdie breeze: Please continue in your own topic – not this one. Your situation is quite different to the original poster’s.

Yes, I agree it was likely one of the techs, that was working on it to help solve the memory 1010 error that was happening post 3.3.1 upgrade, in the media library…but so, it is a problem that started with and around 3.3.1 issues and others working on it.

I did start my own topic the other day – no replies

Thanks Kevin, your advice seems to apply to my case.

@esmi I tried replaced w-admin and wp-includes from a freshlyy downloaded wordpress file, with no change. I also replaced the themes and plugins folder from the fresh wordpress folder (I haev a backup of course). Is replacing the folder different than resetting the folder? Or could there still be an internal setting somewhere that is trying to call up my old theme/plugins?

@kevin, yes I had been thinking about changing the name to /blog, or maybe even it’s own complete url. But right now, this blog is more of a personal recipe & project keeper than something that I am looking to generate a ton of followers to. So I’ve been more focused on trying to work out the kinks and get a look I love before taking it any further than that.

I placed the .htaccess file in the /wordpress directory and now receive an “Internal File Error” message, and am not able to see anything on the permalink page but an “Internal File Error” message as well.

What does your .htaccess file say. Is it empty or has it been modified?

@kevin, it just lists the ftp directory