MX Linux Forum

This may be a bit far afield for this forum but I think this problem may be os related. I run mx-23.6 on two laptops (Dell inspiron 15, 5000; and lenovo ideapad 330) Both are internet connect via ethernet but the problem persists if I switch to wireless. I use firefox on both machines but have tried using chromium on the dell. When trying to reach a particular commercial web site I get a 403 error. I can connect no problem with my phone using either a samsung or firefox browser but the companies mobile interface is really poor. I can connect on my kindle but same problem only larger. My wife can connect using the same network on her windows 10 machine using either firefox or chrome. I've cleared the cache, refreshed repeatedly, rebooted, there are no cookies for this domain that I can identify and kind of don't want to dump every cookie on the machine(s) just to be sure. All other web activity proceeds normally and the mx os performs perfectly (as per usual.) in all other regards. This is very UNimportant but the behavior flumoxes me and I was wondering if anyone had any ideas.

Is the firewall on? Turn that off first, see what happens.

Also, if you are using a VPN turn it off.
Please post the website you are trying to reach.

Is there a simple command line instruction to disable (and subsequently enable) the default firewall in MX-23?

Olums.com (with or with out www., http, or https)

I do not use a vpn

I am also getting

403 Forbidden
You do not have permission to access the requested resource.

Cluster Server: SDL71



https://www.isitdownrightnow.com/olums.com.html says it is up and reachable by them.


I have nothing firewall vpn, nada.

I wager it is ISP related. Or THEY are blocking my IP. But all I can do is guess.

Eadwine Rose wrote: Sun Aug 31, 2025 11:06 am I am also getting

403 Forbidden
You do not have permission to access the requested resource.

Cluster Server: SDL71



https://www.isitdownrightnow.com/olums.com.html says it is up and reachable by them.


I have nothing firewall vpn, nada.

I wager it is ISP related. Or THEY are blocking my IP. But all I can do is guess.

I get the same result, however it is reachable in Win 11 but with a distinct delay before the connection is established.

This is another website with either a misconfigured web server or they are specifically blocking out linux. (I will try in a bit from a mac and report back. )

I changed my useragent in firefox and got right in ;-/

If you want to override their policy / problem, you can make your firefox emulate that it is on windows, buy doing the following:

In the firefox addressbar type in about:config and hit enter.
Agree to the warning
Once in settings, search for


You should see a box with that name in it, several radio buttons and a + sign. Click on the String radio button, and then click the plus. In the field that appears, put in the following:
You should restart firefox and then try to hit the website - and it should load. There MAY be something later on in the website which fails, ( specifically a cookie setting: dialog / page not showing, cart not working properly etc etc.), but typically things will work just fine, its just a problem on the initial "check on who is coming to the website."

Basically those who designed it weren't thinking?

I'm no longer getting a 403 error but am getting this message.
You can wait until the site is fixed or use CharlesV's suggestion (worked for me).

I'm accepting CharlesV's post as the answer. When I have more time I will try to follow his suggestion. Meantime I' about to dump $8K on these people so I will take the time to suggest that they have a look at whom they might be missing out on with such an exclusionary policy. thanks, all!

You'll have to mark his reply as the solution, not your own first post then

@whbr

Tried with Cromium (still from MX) and got:



That's after entering olum.com in the address bar
Someone is very confused (could be me)

Mike

The site was olumS.com

Eadwine Rose wrote: Tue Sep 02, 2025 7:48 am The site was olumS.com

And I can confirm that it still doesn't work without @CharlesV's hack.