WordPress 404 Error On Wp-Admin

1,861 users here now

MODERATORS

  • mkosmo Permanently Banned
  • AutoModerator Master of All Trades
  • BotBust
  • bandman614 Standalone SysAdmin
  • highlord_fox Moderator | /r/sysadmin Sock Puppet
  • VA_Network_Nerd Moderator | Infrastructure Architect
  • Lord_NShYH Systems Architect
  • preperat
  • cryptic_1 It is always DNS
  • bad0seed Trusted VAR
  • . and 5 more »

Welcome to Reddit,

the front page of the internet.

and subscribe to one of thousands of communities.

submitted 2 years ago by free_ryde5_lyfe

Want to add to the discussion?

[–]AmorFati7734 1 point 2 points 3 points 2 years ago (5 children)

[–]free_ryde5_lyfe [S] -1 points 0 points 1 point 2 years ago (4 children)

[–]AmorFati7734 0 points 1 point 2 points 2 years ago * (3 children)

[–]free_ryde5_lyfe [S] 0 points 1 point 2 points 2 years ago (2 children)

[–]AmorFati7734 0 points 1 point 2 points 2 years ago (1 child)

[–]free_ryde5_lyfe [S] 0 points 1 point 2 points 2 years ago (0 children)

  • apps & tools
  • Reddit for iPhone
  • Reddit for Android
  • mobile website

Use of this site constitutes acceptance of our User Agreement and Privacy Policy. © 2019 reddit inc. All rights reserved.

REDDIT and the ALIEN Logo are registered trademarks of reddit inc.

π Rendered by PID 28513 on r2-app-01881d8019a168804 at 2019-03-06 01:48:01.961505+00:00 running 18245c6 country code: SK.

How to Hide Your WordPress Login Page From Hackers and Brute Force

WordPress login page is one of the most vulnerable website part. Of course, hackers perfectly know about it. That’s why your main priority, as a website owner is 100% login page protection.

There are dozens of solutions over the internet – different by complexity and implementation time. In this article, we will discuss the protection of your login page using plugins.

Table of Contents

Why do we need to protect WordPress login page?

You can access login page using one of the following options:

  1. By enter wp-login.php to the browser address bar;
  2. By following the wp-admin link.

In case you haven’t signed up, you’ll see authorization form.

The problem is that everyone (including hackers) know these addresses (links). Hackers create special bots trying to bypass website security, determine website’s CMS and to brute-force the login and password on wp-login and wp-admin pages.

Why are they want to hack into your site?

After accessing authorization page robots try to find the valid match of login and password – they check “Remember me” flag, “Sign in” button and start collating the passwords.

Now imagine the total load on your website during each of this collating attempt and pressing the “Sign in” button! Regular users may have trouble accessing the website. It is caused by robots attempting to find the valid match. This scheme is called “brute-force attack”.

The easiest way of protecting the website from brute-force attacks is to create a unique address of login page, which means using some other URL instead of wp-login or wp-admin. One more important thing: when accessing standard login pages “404 error” should be displayed. In this case, bot seeing the error simply leaves the website. Very smart and simple method!

How to protect WordPress login page using the Clearfy plugin

For the protection purposes, we are going to use one of our free plugins. First of them is Clearfy with embedded feature of protecting WordPress login page. There are also many useful functions in the plugin designed for website protection, optimization (including SEO) and speed improvement.

Protecting wp-admin folder

After you download the free Clearfy plugin, set it on the WordPress settings menu, you’ll see “Clearfy menu”. Then go to the “Defense” section, scroll down and search for the following phrase: “Protect your admin login”.

To disable access to the login page using wp-admin you can simply enable “Hide wp-admin” option and save settings.

Now each time you open wp-admin page you’ll get “404 error” message – the page doesn’t exist.

Protecting wp-login.php URL

To block wp-login.php access, you should just to turn “Hide Login Page” on. However, you should define a new address of login page before hiding the existing one. If you’ll try to hide authorization page without defining new address, the plugin won’t let you do that due to its special inner protection algorithm. Even if you enable the option and leave the field blank, your login page will still be accessible via wp-login.php:

Only when you define the new address, this feature will work.

Let’s define the new address and see how it works. For example, you’ve already entered the new address and saved the settings. We see that now the address of the login page is the following:

IMPORTANT: You should keep this new address and recovery link somewhere safe!

After changing login page, you’ll receive an e-mail from Clearfy plugin with the link to your new login address and the alternative recovery link.

Now let’s check how it works.

  1. Enter wp-admin and try to log in. You’ll get “404 error”;
  2. Copy the new login link and paste to the address bar;
  3. You’ll see authorization page. Everything works perfectly.

Changing access error type

By default the access error after activating the aforementioned options is “404 not found” but you can change it. Let’s set the “Access error type” to “Redirect to” and write some custom URL:

After saving settings, every attempt to access to wp-admin or wp-login.php will redirect bot or user to custom URL.

You can also set the “Forbidden 403” error instead off 404. Attempting to access to wp-admin or wp-login.php, user or bot will get something like:

It imitates that the website is not available, or authorization page doesn’t exist. However, you do know that the access to the website exists but only for you.

Protection of login page using WordPress Hide Login Page plugin

Our second plugin is much smaller than Clearfy. However, if you don’t need a fully-featured plugin, and protection of login page is your only goal, then you can easily install our small plugin named Hide Login Page

It has only one login page protection function and the same options as in Clearfy.

Conclusion

In this article, we’ve told why it’s important to protect WordPress login page and have shown you how to use our plugins for this. You can choose Clearfy or Hide My Login plugin in your case.

Always keep in mind that timely and reliable protection of your website save you a lot of time and money.
Cheers!

[Resolved] 404 Error on Category Pages

Hi, Amit here, I am the WPML Support Manager, our current ticket queue is high, update your WPML plugins before reporting tickets – our recent release resolves a few known issue

All of the known issues are documented in https://wpml.org/known-issues/ you can also use our support search to find helpful information and of course review our documentation before opening a ticket.

If you do need to open a ticket please make sure to provide us with all the needed information as described here https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/

This is the technical support forum for WPML – the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This thread is resolved. Here is a description of the problem and solution.

solution is described here

This topic contains 14 replies, has 5 voices.

After updating WPML to the latest version, I started seeing 404 errors across all of my category pages. The top page and post pages work properly, only category pages die.

I have an Japanese/English website and this is what I figured out after trial and error.

If I set language selector to Japanese on WP Admin panel, and update permalink structure, then the Japanese category starts working, but the English category page becomes 404 not found. If I set language selector to English on WP Admin panel, and update permalink structure, then the English category starts working, but the Japanese category page becomes 404 not found.

In other words, category pages is always working on one language, but is completely broken on the other language at any given time.

Can you please advise on this matter?

I found out that plugin, WP No Category Base – WPML compatible, is causing this problem. Apparently, this plugin is no longer compatible with your latest WPML version.

Do you have any other recommendations on a plugin that can remove category base that is also compatible with the latest version of WPML?

I have the same problem!
With WP No Category Base – WPML plugin disabled everything is working.

Now, we should do what.. redirect the old category names like blog.com/category-name to blog.com/category/category-name??

This is not the best option.

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

I am Konrad, WPML developer and I will try to help you.

I see that this plugin is not at our compatibility list ( https://wpml.org/documentation/plugins-compatibility/ ) but if you said that it worked before 3.1.9,3, it means that we did some regression in our code.

I will try to find now what we did and fix this / provide you solution. I will update this ticket when I will find anything. Feel free to write if you have any other suggestions

Hi Konrad,
Thank you for looking into this problem.
I look forward to hearing from you.

I am also experiencing this issue.
A resolution to the issue would be greatly appreciated!

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

Do you remember from which version did you updated WPML plugin?

I confirm that I see 404 on translated categories with this additional plugin.

But I cannot find WPML version when it was ok: I tried 3.1.8.4, 3.1.9, 3.1.9.2 (current version is 3.1.9.3) and every time i see the same result with 404 error page (I am refreshing permalink structures every time).

Could you provide WPML plugin version before update?

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

Meanwhile I contacted with our compatibility team. And probably I don’t have good news.

It is actually not regression issue. We know for long time that this plugin does not work with WPML, returning 404 error pages and it happened in the past too. So this issue is not anything new.

Normally if we see that some plugin does not work, we move it to our compatibility team, then they contact with plugin author and ask if he want to cooperate in fixing the issue.
But we already tried to contact with author and he was not responding.

So probably we cannot do anything. If you want us to contact again with plugin author, please say.

Our official sugegstion for now is to not use this plugin at all. Here are other options:

1. please try this solution: hidden link

2. if this does not help, SEO plugin has option to remove category base, see this description: hidden link

Please let me know if I can help you with any other questions you might have

I tried to find out the last version of WPML that worked correctly, but I found out that I cannot replicate the same environment anymore. All I know is that the plugin has been working perfectly fine for a long time in my environment, despite WPML devs say that this plugin does not work with WPML.

I have tried all of your solutions, but they did not work.
-FV Top Level Cats plugin
-Changing permalink structure
-SEO Plugin

Can you ask your compatibility team to contact the plugin author one more time and ask if the author can cooperate in fixing the issue?

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

Ok, I understand you. I am moving this to our compatibility team. The standard action at forum is to close ticket so I am doing this as well. But if I will have any updates, I will reply immadietly.

Please also remember that it can take a while (if i remember clear author of this plugin was not responding) or even finally he would not agree to cooperate. In this case we cannot do anything more

We’ve also noticed some of the same problems recently and using the WP No Category Base – WPML compatible plugin, the FV Top Level Categories plugin or WordPress SEO no-category base settings doesn’t solve things. We only had issues with sub-categories though.

Digging a bit deeper, it seems the WP No Category Base author suggests using https://wordpress.org/support/plugin/remove-category-url, but this didn’t work for us either at first. Looking at the plugin forum, it seems like one of the WPML staff members have come up with a fix for this plugin though https://wordpress.org/support/topic/404-in-translated-categories-with-wpml-3191?replies=5, which is also mentioned here on the forums https://wpml.org/es/forums/topic/los-enlaces-a-las-categorias-se-rompen-despues-de-haber-actualizado-wpml/

Modifying the plugin file with this fix made this plugin work for us. Hopefully the fix will be included in future updates!

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

This topic is closed as resolved and to help you I need to ask you to open new one. Could you do this? 🙂

Sorry, didn’t see it was marked resolved, as it was quite a recent topic. Anyway, my post just had a couple of pointers to how this issue could be fixed, which might be useful to others following this topic.

Languages: English (English )

Timezone: Europe/Rome (GMT+01:00)

Ok, i missed your last paragraph 🙂

Hi Jesper,
Thank you for the information.
I’ve tried out Remove Category URL 0.1.2, and it’s working like it was before!

Leave a Reply

Your email address will not be published. Required fields are marked *