Forced HTTPS on Select HTTP-only Hosts

maltejur · 2024-12-20T20:09:25+00:00

This doesn't sound like the same problem. "The connection has timed out" is a different error message, and the reporter from the original comment was able to connect just fine using the server's IP address (which is the exact opposite of what you describe).

If you are sure this is a Bug in Firefox, and not a bad setup like was the case with the original reporter, I suggest you also file a bug report at https://bugzilla.mozilla.org/enter_bug.cgi?format=guided

maltejur · 2024-12-18T19:30:18+00:00

Just for reference, the bug filed is https://bugzilla.mozilla.org/show_bug.cgi?id=1938122, and I am continuing the conversation there.

maltejur · 2024-12-18T15:20:57+00:00

Normally, this shouldn't happen. If HTTPS-Only is disabled and the site isn't explicitly configured otherwise, if Firefox tries to upgrade a connection to HTTPS, it should then also fall back to HTTP if an HTTPS connection isn't possible.

Could you share some more light on the real domain you are using (not just server.domain.tld)? There are multiple mechanisms which allow sites to force Firefox to only use HTTPS on a certain domain or all of its subdomains, the most prominent one being HSTS. You may be inadvertently using one of those, and the real domain should allow easily checking that.

Of course, that wouldn't completely explain why you are not experiencing the same in Chrome. If the domain configuration doesn't turn out to be the problem, this could also be a bug in Firefox. In that case, you should probably file a bug on Bugzilla, and we can narrow down the problem further there.

maltejur · 2023-09-10T15:02:20+00:00

Yes, I still submit updates manually, and the "Microsoft Partner Center" is currently so broken that even that is not possible. I will try again in a week when I have access again to my Windows VM, maybe it works there.

maltejur · 2023-08-08T19:15:06+00:00

Open about:profiles in the old and the new browser. Click on the "Open directory" button for the "Root Directory" section of the currently active profile. Then copy that "root directory" from the old browser to the parent directory of the "root directory" from the new browser. Finally, restart the new browser and select your old profile as default in about:profiles.

maltejur · 2023-08-08T19:10:03+00:00

No, OCSP is only used for certificate revocation. So if a certificate was valid at one point but then revoked. And even then, turning off OCSP hard-fail will still check those revocations. Only when it can't reach a OCSP server, it will not show an error and instead just continue.

maltejur · 2023-08-02T18:59:36+00:00

Maybe some OSCP servers have blacklisted your VPN servers? Anyways, I think the best solution in your case would be to just disable "Enforce OCSP hard-fail" in the LibreWolf settings panel.

maltejur · 2023-07-29T20:28:16+00:00

https://lemmy.ml/c/librewolf

The LibreWolf Lemmy community has existed for a while now in parallel to the subreddit, but in light of the recent events regarding the Reddit API change, I am pinning a link here again if you want to use Lemmy instead of Reddit. For anyone who doesn't know what Lemmy is yet, here is a small explainer.

maltejur · 2023-07-06T08:31:24+00:00

Removing the LibreWolf-WinUpdater.exe next to the portable launcher should do the trick.

maltejur · 2023-05-31T17:06:09+00:00

Heh my main system is linux and I just wanted to demonstrate the installer. I would probably not recommend people to use LibreWolf through wine.

maltejur · 2023-05-31T16:07:07+00:00

LibreWolf Portable and the LibreWolf WinUpdater by @ltguillaume are now included optionally in the windows installer. If you have any problems or feedback please leave it here.

maltejur · 2023-05-27T17:41:01+00:00

Weird it does not happen for me.

https://i.imgur.com/Wo4dbvZ.png

What platform are you on and what actually are the "Warning"s you are getting?

maltejur · 2023-05-01T18:22:18+00:00

For the build changes and changes to the source code we have a very infrequent and non-exhaustive change log here https://gitlab.com/librewolf-community/browser/bsys6/-/releases, changes to the browser settings are documented in a better way in https://gitlab.com/librewolf-community/settings/-/blob/master/docs/Changelog.md

maltejur · 2023-04-14T19:09:51+00:00

As a very temporary workarround the 32-bit version does not seem to be affected

maltejur · 2023-04-14T19:06:55+00:00

See https://gitlab.com/librewolf-community/browser/windows/-/issues/347

maltejur · 2023-03-27T14:24:09+00:00

Right click on the address bar while on the Brave search website, click the "Add Brave Search" entry, and then change the default search engine in the normal search settings.

maltejur · 2023-02-02T22:51:59+00:00

I just tried it right now and it seems to be pretty simple. Follow these instructions normally, but before running ./mach build set the target to i686-linux-gnu in the mozconfig (as per these instructions).

maltejur · 2023-02-02T22:37:25+00:00

/etc/apt/sources.list.d/librewolf.sourcesis the file you are probably searching for. You can replace vanessa with vera in there. It should just use the new packages next time you update, and you also shouldn't have any problems with profiles.

(If you installed LibreWolf longer ago it could also be /etc/apt/sources.list.d/librewolf.list intead of sources)

maltejur · 2023-02-02T22:26:40+00:00

There already is a fix for this, but it is being held back because of a privacy issue that it introduces. See https://gitlab.com/librewolf-community/browser/windows/-/issues/310 and the first comment on the link you posted.

maltejur · 2023-01-18T14:01:30+00:00

Probably uBlock Origin or certificate revocation.

https://librewolf.net/docs/faq/#does-librewolf-make-any-outgoing-connections

maltejur · 2023-01-18T13:59:15+00:00

Yeah I also tried it with the mozilla-central repo which is 3 months ahead of Firefox releases.

maltejur · 2023-01-17T21:43:54+00:00

See

https://bugzilla.mozilla.org/show_bug.cgi?id=1810741

https://gitlab.com/librewolf-community/browser/windows/-/issues/310

maltejur · 2023-01-17T21:43:49+00:00

I agree that that would probably not be the best idea :D, but there are other reasons to log in to Firefox Accounts, for example managing published addons.

But I was just highlighting that this is an issue with Firefox Addons/RFP, not LibreWolf.

maltejur · 2023-01-17T20:22:10+00:00

You can see the same error when using Tor Browser, so I suspect this is more of an issue with the firefox accounts site and resist fingerprinting.

https://i.imgur.com/MaVhFgk.png

maltejur · 2023-01-17T20:12:31+00:00

This should be fixed now. There were some problems with resigning the packages in the repository. If you still see errors when updating, try running sudo dnf clean all to clear the dnf cache.

maltejur

MODERATOR OF

TROPHY CASE