Need help?

Our experts will login to your server within 30 minutes to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price per month.

Failed to start firewalld service unit is masked – How we fix it!

Are you stuck with failed to start firewalld service unit is masked? We can help you fix it.

Masking the firewall service will stop it from automatically starting.

Here at Bobcares, we often receive requests regarding firewalld as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix the errors related to firewalld.

 

Causes for failed to start firewalld service unit is masked

We mask the firewall to prevent the firewall from starting from other services.

This error occurs when we try to enable the firewalld that is masked.

The error can also occur if the mask symbolic link is broken.

We resolve the error by unmasking the firewalld and starting the service.

 

How to fix failed to start firewalld service unit is masked?

Recently one of our customers contacted us saying he was unable to enable firewalld in the server. And also was getting the same error.

Now let’s discuss how our Support Engineers resolve the error for our customers.

 

Unmask

On analyzing the firewalld service we found a mask firewall set. Thus to resolve the error we unmask the firewalld service. We can enable the firewall service if it is not masked.

To unmask the service we use the command

systemctl unmask --now firewalld

After executing the command we get the output as

failed to start firewalld service unit is masked

Now we enable the firewalld service using the command

systemctl enable firewalld

Finally, we start the firewalld service using the command

systemctl start firewalld

 

Mask link is broken

One of the common reasons for the error is when starting the service the masked link is broken. Thus we need to link the mask location once again to resolve the error.

To unmask the service we use the command.

systemctl unmask firewalld

Thus, if the service still fails to unmask we need to manually mask it first. The location will change based on the Linux flavors.

ln -s /etc/systemd/system/firewalld.service /dev/null

Thus we unmask it. Then we start the service using the command

systemctl start firewalld

Finally, we find the status using

firewall-cmd --state

 

Failed to start firewalld service

If the above solution did not fix the error. We need to analyze the logs to determine more details about the error.

Our Support Engineers find more information using the command

systemctl status firewalld.service

We find further information from journalctl -xn

Thus, our Support Engineers find the reason for the error and resolve the error accordingly.

 

[Need any further assistance with firewalld errors? – We’ll help you]

 

Conclusion

In short, we’ve discussed the causes of the error. Also, we’ve discussed how our Support Engineers resolve the firewall mask error for our customers.


PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Submit a Comment

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

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF