Why Your Firewall Worked Yesterday but Not Today

Problem Overview

One day everything is fine. Staff are online, email flows, the card machine talks to the bank, and the phones ring. The next morning nothing connects, or only some things do, and the only piece of equipment that handles all of that traffic is your firewall. When a firewall stopped working overnight with no obvious reason, it feels like the device broke on its own. In the field, that is almost never what happened.

Your firewall sits between your office network and the internet. Every website, email, payment, and phone call passes through it. It also enforces rules about what is allowed in and out. Because it touches everything, a small change to it, or to the equipment around it, can look like a total failure. The good news is that a firewall that worked yesterday and fails today usually points to a handful of common, fixable causes rather than a dead box. This guide walks you through them in plain language, in the order a technician would actually check them.

Common Symptoms

• No internet anywhere in the office, even though the modem lights look normal.
• Some devices or services work while others do not (for example, web browsing works but email or a payment terminal does not).
• Staff suddenly cannot reach an app or website they used yesterday, and get a blocked or timed-out message.
• The VPN that remote workers rely on will no longer connect.
• The firewall admin page is slow to load, will not load, or you cannot log in to it.
• A warning light on the firewall is red or amber instead of its usual color, or a light that is normally on is now off.
• Internet drops out and comes back repeatedly throughout the day.

Most Likely Causes

• A recent change. Someone added a rule, changed a setting, swapped a cable, or installed new equipment near the firewall. This is by far the most common reason a working firewall stops working, even when no one remembers changing anything.
• An automatic update or reboot overnight. Many firewalls install firmware updates or restart on a schedule. An update that did not finish cleanly, or a reboot that left the device in a confused state, can break connectivity until it is power-cycled.
• An expired license or subscription. Business firewalls often need an active security subscription to pass traffic or run their filtering features. When that lapses, the device can start blocking traffic or stop working as expected.
• A power or hardware hiccup. A flickering power supply, a loose power cable, an overheated unit in a hot closet, or a failing power adapter can cause a firewall to lock up or behave oddly.
• An internet outage from your provider. Sometimes the firewall is fine and the line behind it is down. The firewall simply has nothing to pass through, which looks identical to a firewall failure from a desk.
• A blocked or changed address. If the firewall lost its internet address from your provider, or a security rule started blocking a service you rely on, specific things break while others keep working.
• Genuine hardware failure. The least common cause. Real failures happen, but they sit at the bottom of the list for a reason.

Step-by-Step Troubleshooting

Work through these in order. Each step is safe to do yourself, and none of them ask you to turn off your protection. Stop as soon as the problem clears.

1. Ask what changed since it last worked. Before touching anything, ask around. Did anyone install equipment, move a cable, change a setting, or get a visit from a vendor or contractor yesterday? Was there a power cut or storm overnight? The answer often points straight at the cause and saves you an hour of guessing.
2. Look at the firewall itself. Walk over to the device. Note the lights and their colors. A normal firewall usually shows a steady power light and one or more activity lights that blink. A red or amber light, or a light that is off when it is normally on, is a clue. Take a photo of the lights with your phone so you can describe them to support later if needed.
3. Check the cables. Firmly reseat the network cables at both ends, including the cable from the modem to the firewall and the cable from the firewall to your main switch. A cable that is slightly loose can look exactly like a dead device. Make sure the power cable is fully seated as well.
4. Power-cycle the equipment in the right order. This fixes a large share of overnight failures. Turn off the firewall, the switch, and the modem. Wait a full two minutes. Turn the modem on first and wait until its lights settle (usually a minute or two). Then turn on the firewall and wait for it to fully start. Then turn on the switch. Powering on in this order lets each device get a clean address from the one before it. Test the internet after each device comes up.
5. Confirm whether the internet line itself is up. Connect a single laptop directly to the modem with a network cable, bypassing the firewall, and see if you get internet. If you do, the line is fine and the problem is the firewall or its settings. If you do not, the issue is upstream with your provider, not your firewall. Reconnect the firewall as soon as you have your answer so you are not running unprotected.
6. Log in to the firewall admin page. Open a web browser on a computer connected to the network and type the firewall address into the bar (your installer usually wrote this down; it is often something like 192.168.1.1). You should see a login screen. If the page will not load at all, the device may be locked up, which points back to a power-cycle. If you can log in, you can keep checking.
7. Look for a license or subscription warning. Once logged in, scan the main dashboard or status page for any banner, red text, or notice about an expired license, lapsed subscription, or required renewal. These messages are usually near the top of the screen. An expired subscription is a common silent cause and is fixed by renewing, not by replacing hardware.
8. Check the firewall internet status. On the same dashboard, find the section that shows the internet or WAN connection. It should show an active connection with an address from your provider. If it shows disconnected or no address, the firewall is not getting a line from the modem, which loops you back to the cable and power-cycle steps.
9. Review recent rule or setting changes. If only specific things are broken, such as one app, email, or the payment terminal, the cause is often a rule rather than the whole device. Look for a logs, events, or recent changes section. If you can clearly see a change that lines up with when the problem started, and you are confident undoing it is safe, you can revert that one change. If you are not sure, leave it and note it for support. Never disable the firewall or open everything up as a shortcut.
10. Write down what you found. Note the light colors, any warning messages, which devices work and which do not, and what you have already tried. If you do need to call support, this turns a long diagnostic call into a short one.

When to Call Support

Call your firewall provider, internet provider, or IT partner when any of the following is true. There is no shame in this; some of these genuinely require their access.

• A direct-to-modem laptop has no internet either. That is a provider issue, and only your internet company can fix the line.
• You see an expired license or subscription notice. Renewing usually has to go through your provider or reseller account.
• The firewall will not power on, will not load its admin page after a proper power-cycle, or shows a red light that does not clear.
• Only specific services are broken and you cannot safely identify which rule changed, or undoing a change did not help.
• The firewall is under a service contract. In that case, let the contract do its job rather than experimenting on a device you may not fully control.
• You suspect a security event, such as unexpected changes you cannot explain. In that case, stop, do not disable protection, and get a professional involved quickly.

Prevention Tips

• Write down your firewall basics. Keep a simple note of the firewall make, its admin address, who installed it, and when the security subscription renews. This one page saves hours during an outage.
• Track the subscription renewal date. Put the license or subscription expiry on a shared calendar so it never lapses by surprise.
• Put the firewall and modem on a battery backup. A small uninterruptible power supply protects them from flickers and short outages that cause overnight lockups.
• Keep the equipment cool and ventilated. Do not stack gear in a sealed cabinet or a hot closet. Heat shortens hardware life and causes random lockups.
• Schedule firmware updates for off-hours and one at a time. Avoid letting updates run unattended during business hours, and change one thing at a time so you always know what caused a problem.
• Log changes. Keep a short shared note of any change made to the network, who made it, and when. When something breaks, this list is the fastest path to the cause.
• Know how to reach the right support before you need it. Save the provider and IT contact details somewhere everyone can find them.

Frequently Asked Questions

Why did my firewall stop working overnight when nobody touched it?

Most often something did change, just not by hand. Many firewalls update their firmware or reboot on a schedule, and an update that did not finish cleanly can leave the device stuck until it is power-cycled. A power flicker, an expired subscription that lapsed at midnight, or your provider doing maintenance on the line can all cause an overnight failure with no human involved. Start with a proper power-cycle and a check for license warnings.

Should I just turn off the firewall to get the office back online?

No. Turning off or bypassing the firewall leaves your business exposed to the open internet, which is a far bigger problem than a temporary outage. It is safe to briefly plug a single laptop directly into the modem to test whether the internet line itself is up, but reconnect the firewall right after. If you cannot restore protection quickly, that is the moment to call support rather than run unprotected.

How do I tell if the problem is my firewall or my internet provider?

Connect one laptop directly to the modem with a cable, bypassing the firewall. If that laptop has internet, your line is fine and the issue is the firewall or its settings. If that laptop has no internet either, the problem is upstream with your provider and only they can fix it. This single test saves a lot of back-and-forth and tells you exactly who to call.

Could an expired license really stop my whole firewall from working?

Yes, it is more common than people expect. Many business firewalls rely on an active security subscription to run their filtering and, in some cases, to pass traffic normally. When that subscription lapses, the device can start blocking things or behaving as if it failed. Log in to the admin page and look for a renewal or expired notice near the top before assuming the hardware is dead.

Related Articles

• Why You Can't Ping Your Firewall
• How to Troubleshoot Internet Outages Before Calling Support
• How to Tell If the Problem Is Your ISP or Your Equipment

The NTC Tech Desk publishes practical, plain-English technology guides for small businesses. If this helped, subscribe for more straightforward troubleshooting guides.