Has anyone got the Mullvad Browser working?

I've started using Mullvad Browser on my Linux and Darwin boxes, but I've had a lot of difficulty in getting it to run on FreeBSD (or any BSD).

Thus far, I've tried running it in jails (Debian 11 and CentOS 7), which crashed my PC; and using the Windows version through emulators/wine, which had no font smoothing and couldn't load any websites.

I considered compiling from source, but this would take too long; using emulators/qemu or KVM, but then I would be unable to access the clipboard and downloads; and using Docker, but I thought the container looked a little sketchy.

Out of curiosity, has anyone here actually managed to get it working on FreeBSD in any capacity?
 
I have using a Debian bookworm jail. I use Bastille for jails because to me it was quick and easy.
It is over ssh and I have not gotten sound to work yet (I have it working in BSD jails), but it works just fine otherwise.
just don't forget to add

Code:
AddressFamily inet
X11UseLocalhost no

to sshd_config
 
Are you planning to keep your port up to date? E.g. when mullvad has a new ESR version?
As arkenfox probably will disappear (hopefully he'll do at least the 153) I am looking for a replacement.
And why was your port rejected?
They not want next browsers to port tree. Long time build , not enough server capacity
 
They not want next browsers to port tree. Long time build , not enough server capacity
This is a funny statement (from them). But I will not start a discussion which
packages could be removed and save a huge amount of server capacity
because this is simply in the eye of the beholder.
Instead they should think how to deal with situations like this (apart from
obtaining more hardware). E.g., one could simply skip ports from making
packages. The few kB that remain on their precious servers will just be
the port's files...
 
This is a funny statement (from them). But I will not start a discussion which
packages could be removed and save a huge amount of server capacity
because this is simply in the eye of the beholder.
Instead they should think how to deal with situations like this (apart from
obtaining more hardware). E.g., one could simply skip ports from making
packages. The few kB that remain on their precious servers will just be
the port's files...
do you know about waterfox ? Is in port tree
 
Back
Top