Sorry I'm confused.  Is the PC your are shutting down the one running the container ?

1 hour ago, Djoss said:

Sorry I'm confused.  Is the PC your are shutting down the one running the container ?

Sorry, i should have explained it a bit better.  I have 2 computers:

PC 1 is the Unraid Machine

PC 2 is my Windows gaming/personal Machine

 

I use PC2 to configure my unraid server (PC 1) and mess with plex/arr's via chrome browser.  I open the Firefox docker (a chrome tab opens with firefox) and i have my airline (southwest) check in page as the homepage.  I enter my information and a countdown clock starts.  When i'm done using PC 2, i shut it down.  PC 1 still stays running (it never shuts down). 

It looks like this before i shutdown PC 2:

When i come back the next morning and fire up PC 2 and open chrome, all my unraid tabs (dashboard/plex/arrs/firefox) automatically open and on the firefox browser, the countown clock and the fields i entered are no longer there. 

It looks like this in the morning (the timer had not expired, it should still have countdown time remaining)

 

My goal with using the docker was so that i could have the browser stay open forever and i could just load all my flight info into it and not worry about remembering to check in.  

 

I hope this explains it a bit better. 

Any ideas?  

Edit: I just noticed there was a docker container update...i just updated,  i'll post if it fixed it. 

 

 

Edited May 23, 20233 yr by danimal86

Also, are you sure it's not the site itself that has an issue when kept open for too long ?

39 minutes ago, Djoss said:

Also, are you sure it's not the site itself that has an issue when kept open for too long ?

I didn't think about that. Any way to track that?

 

I think for the most part i'll just have to set it up the day of....Not the biggest issue in the world.  Thanks for your help

You can try to open a new tab and start a stop watch at https://www.online-stopwatch.com/.  This will at least confirm that there is no issue with Firefox itself.

10 hours ago, Djoss said:

You can try to open a new tab and start a stop watch at https://www.online-stopwatch.com/.  This will at least confirm that there is no issue with Firefox itself.

Thats a great idea!  I've got it running now.  

I just checked on it, and the stopwatch had reset itself to the Stopwatch or Countdown homepage.  So it seems like it is something with firefox resetting.  

18 hours ago, danimal86 said:

So it seems like it is something with firefox resetting.

Do you backup your appdata?

On 5/28/2023 at 8:16 AM, JonathanM said:

Do you backup your appdata?

Dang, i didn't even think about this.  Yes i do, i remember running into a problem with Lucky Backups that it would disconnect when my appdata backups, nightly.  

I'll set it to Exclude the Firefox appdata folder during my daily backups.  

@Djoss I bet this is the problem.  Going to try the stopwatch again.  

On 5/28/2023 at 8:16 AM, JonathanM said:

Do you backup your appdata?

i tried using the stopwatch and it had reset itself, so it wasn't the appdata backup

I'll give it a try again and see if it will not reset overnight.  

 

Edit: it reset overnight

Edited June 2, 20233 yr by danimal86

Got it figured out.  Go into CA Backup Appdata v2.5 and uder the Backlup/Settings tab, go down to the bottom to Show Advanced Settings, and uncheck Firefox to stop when backing up appdata.  

Is there a timer that resets everything in this sandbox/firefox?

 

Today when i woke up, all bookmarks/history were gone. No backup plugins were running.

Running latest version.

Best Regards

3 hours ago, Jawnyboy said:

Is there a timer that resets everything in this sandbox/firefox?

 

Today when i woke up, all bookmarks/history were gone. No backup plugins were running.

Running latest version.

Best Regards

 

No, nothing resets everything  You can check the uptime of the container to see if it has been restarted.

Hello, I've started to get the following error when the docker is booting

 

[xvnc        ] Fatal server error:
[xvnc        ] (EE) vncExtInit: failed to bind socket: Address in use (98)
[xvnc        ] (EE)
[supervisor  ] service 'xvnc' failed to be started: not ready after 5000 msec, giving up.

 

I have the traffic running through binhex-qbittorrentvpn, which was working perfectly until I did 2 things.  I changed the end point on the VPN and I installed the Opera docker, so I could test my Internet connection without running through the VPN.  I'm going to assume the end point change isn't the issue, as binhex-qbittorrentvpn is running fine and so is everything else that is running through it.

 

Any help would be great as your version of Firefox is excellent

 

PS If I run the traffic normally through bridge, it works fine.

 

So after some tinkering myself, I thought I had fixed it by just changing the Firefox port in binhex-qbittorrentvpn, but that failed so when changing them back, it rebuilt and then was working.  But this caused another issue of when opening Nicotine+ which is a totally different port.  It would display Firefox.  I'm so confused.

Edited September 27, 20241 yr by will1565

Just a heads up, The most recent version v25.09.1 was causing the first tab to attempt to open to 127.0.0.1 despite other urls set. I presume it is related to this change:

https://github.com/jlesage/docker-firefox/commit/6a5d2365d8b7d44fbb9c38889cb4529c718f761e#diff-0bc14dd397db5d7da683201b8b1aa9ee10a9a07e86e10415fe02828d4437c9a2 which changes the ordering startup tabs and FF_CUSTOM_ARGS. Since the default config passes in 0 as FF_CUSTOM_ARGS.

For anyone struggling with this, simply remove the FF_CUSTOM_ARGS flag in the Unraid UI for the container.

Thank you, I fixed the template!

Hi,

I want to run isolated firefox browsers, and added a custom docker network to run a firefox container. It works, but is quite sluggish, especially when first time loading a home page. The server includes a AdGuard Home/Unbound dns setup. The firefox container passed traffic thru

Docker DNS (127.0.0.X)

which is the suspected reason why browsing is sluggish. Forcing --dns 10.10.50.60 in Extra parameters brakes the container.

Running macvlan in the server.

Any recommendation how to setup?

//F

How do I get the most recent version of Firefox?

Image = v145.0.

Release = v147.0.

On 1/24/2026 at 1:04 PM, Jaybau said:

How do I get the most recent version of Firefox?

Image = v145.0.

Release = v147.0.

This container is based on Alpine Linux. Currently, 145.0 is the latest version available from the latest Alpine Linux stable repo: https://pkgs.alpinelinux.org/packages?name=firefox&branch=v3.23&repo=&arch=x86_64&origin=&flagged=&maintainer=