I installed a Drupal 7 site on my local server just to learn,
After 10-15 incorrect log in attempts my local IP has been blocked.
Sorry, too many failed login attempts from your IP address. This IP address is temporarily blocked. Try again later or request a new password.
Screenshot of my local site:
As per articles:
I erased flood table.
flood Table:
Checked blocked_ips and found nothing.
blocked_ips table:
I want to remove the limit of failed login attempts block.
If you cleared flood table your user is unblocked for sure. However it seems that you forgot your password just resend it again if you have mail server setup up in local. If not, Reset the administrator password with sql-query > https://www.drupal.org/node/1023428
Login Security module will allow you to control number of failed attempts before blocking https://www.drupal.org/project/login_security
Related
I've issues connecting to my cpanel as it keeps bringing ip address change. i have tried using other browsers and even vpn but to no avail. I've been battling this issue over a week now. i will be delighted if anyone can help me out
This issue is caused when a user logs in, and then the IP address that they are accessing cPanel from changes.
This change is detected by a setting named 'Cookie IP Validation'.
WHM: Home -> Server Configuration -> Tweak Settings
Option: Cookie IP validation
Check This Link
Scroll down for 'Cookie IP Validation' for more information.
In Tweak Settings, by default, this setting is set to 'strict'.
Changing the value to 'loose' should allow you to be connected.
If you still continue to get disconnected from cPanel or WHM, change the value to 'disable' to stop it entirely.
I am having a mild panic attack and could use some help.
I was emailed by Google telling me I need to change my machine type in my VM Instance. So I logged in, it told me I needed to stop the instance to make that change. I stopped the instance and then realized I'm not using the deprecated F1-Micro, so I just hit Play to restart the instance.
It restarts, has the reassuring green symbol, but my wordpress site can't be accessed.
I tried connecting via SSH and it seems like the data is there, I can navigate to the wordpress folder.
Can someone please advise on what I need to do to get the site running?
Thanks!
EDIT: More Info
Checking status of NGINX server shows it is "active (running)"
When visiting the web address, it loads for a very long time and then goes to an error page that just says "This site can't be reached the site took too long to respond. try checking connection and the proxy and the firewall. ERR_CONNECTION_TIMED_OUT"
I found the issue.
The Google documentation suggests your IP address will remain. Whether that is standard or not, my IP address changed, so once I updated my DNS records I was back online.
I am an email server noob. I own a domain 'mydomain.org' and I'd like to forward emails sent to that domain to other email address, perhaps at 'gmail.com' or 'university.edu'. I thought I set this up right, but my email log is giving me errors like this:
connect to mx1.university.edu[171.67.219.71]:25: Connection timed out
and
Dec 22 05:17:24 mail-server postfix/smtp[6370]: connect to alt1.gmail-smtp-in.l.google.com[2607:f8b0:400d:c00::1a]:25: Network is unreachable
I don't know too much about this, but I imagine there must be some kind of authentication that I need to set up, but I'm shy of the laundry list blog posts. Does this look like "authentication stuff"? If so, what do I need to set up next? If not, any idea why the receiving mail servers drop my server?
Yes, network issue. For future folks, Google does not allow outgoing connections for SMTP servers, maybe to prevent spam? Here's info about how to set that up: https://cloud.google.com/compute/docs/sending-mail
I have a situation where a 2008 server with IIS7 has been application level compromised and is sending spam from port 25. We have ran a virus scan and removed the infected files yet the spam is still being sent.
We know the spam is coming from a local file as the firewall has port 25 blocked inbound and the SMTP log is showing all requests appearing from the local server. We have ran a LogParser scan of the sites (which there are many) for any POST data to files on the server but the results all look genuine. The PID sending the data on port 25 is simply inetinfo.exe so this isn't much use either.
I would like to identify what file is sending this e-mail, can anyone think of a way to do this?
Have you shut down the smtp server under properties for local outbound? meaning 127. etc...? also, have you looked in the que folder under inetpub to see if the offending message is in there? In some cases a file can change the remote server on smtp in IIS to send via aproxy or some other service so it would ignore your scans.
in addition, not all mail has to use port 25 to send emails. it can hit any port if the creator tells it to.
I have a networking question. I've setup my own server. The server is up and running. But I must give people inside my network the server's local IP address for better downspeed, because when my network clients using internet, the server's upspeed is slow.
I think giving ip address to my users is pretty odd and hard to remember. Is there any way to allow a same domain name access the server, where the LAN users access via local ip address (ex: 192.168.1.99) and internet users via a static ip address (ex: 111.111.111.111), but with same domain name?
I've made a flow chart, if you don't fully understand my question.
Users on local network and on the internet type the same domain: example.com
If you can recognise 100%, wheter a user is internal or external (e.g. set up a list with internal user accounts), you can use only the internet site, and redirect internal users to the internal IP address after they logged in. They will use the site thru the internet only before they're not logged in, I think, it's acceptable. Don't forget, when redirecting users from example.com to 192.168.1.99, all the cookies will be "lost", the user's session will be cleared, which thing you have to solve it somehow (say, redirect to the local site with a magic parameter, which re-initializes the session on the 192.168.1.99 server).
It has one withdraw: your users listed as internals can't use the site from other place, say, from home. It can be solved by placing to them (and only to them) a direct link after they logs in ("click here if you're not in the office"), which forces the use of the internet site (example.com), or you can solve it by JavaScript (requesting some data with AJAX from 192.168.1.99, and if it fails, don't redirect the user to 192.168.1.99 - maybe it is a bit more difficult).
Edit, suggested by #glglgl: Check client's IP address to see, wheter the request has been initiated from local network or over internet. (See comments.)