Initializings fail + impossible to open web pages

[pharaonic-faery]

• Temporary Containers Version: 1.9.2
• Firefox Version: 114.0.2 (64 bits)

Actual behavior

On Firefox startup, Temporary Containers (TC) doesn't work. After reinstalling TC, when I enter a URL in the address bar of Firefox, or when I click a link, nothing happens. If I click a link while pressing the Ctrl key, a new tab opens with the correct URL in the address bar but the page doesn't load.
This misbehavior happens only if TC is enabled.

Expected behavior

I want web pages to load if I enter their URL or if I click a link pointing to them.

Steps to reproduce

NB: Everytime "click" occurs in the following, you should understand "left-click":

1. Open Firefox with a clean profile, except that TC has already been installed, is enabled, and the preferences in the attached "TC_preferences.txt" file below have already been imported.
2. TC doesn't work and there is a E in a red square on its toolbar icon. Click the TC toolbar icon, then click "Reload Add-on and hope the best". The E on the red background remains and TC still doesn't work.
3. Click the toolbar icon of TC, then click "Uninstall Add-on and open it on addons.mozilla.org, where you could try installing again". A window pops up and asks "Uninstall?". Click "OK", then "Add to Firefox", then "Add".
4. The TC settings page opens. Click the "Export/Import" tab, then "Import from local file". Choose the "TC_preferences.txt" preferences export file below after downloading it, then click "OK". The E on the red background disappears.
5. Enter any valid URL in the address bar, for example: https://github.com/stoically/temporary-containers
6. Press "Enter". Nothing happens.
7. Open the Firefox homepage by opening a new tab, and click any link there: nothing happens
8. Do the same while pressing the Ctrl key: a new tab opens with the correct URL in the address bar but the page doesn't load.

Notes

step 2: If any page beginning with about:debugging#/ is open in Firefox (for example: about:debugging#/setup or about:debugging#/runtime/this-firefox), then when you click "Reload Add-on and hope the best", the red E disappears, and you can access the settings. So it seems you don't have to reinstall TC. Skip to step 5. The behavior remains the same as described above.

---

• preferences export file: TC_preferences.txt
• no debug log provided since nothing appears in the debug console while reproducing the steps above.

[sheddup]

I had similar issues when Firefox upgraded to 115 ESR, the fix was to change the Container Number from "Hide" to "Keep counting until browser restart" (your TC_preferences.txt show that you are using the Hide option)

[pharaonic-faery]

Yeah! It works! Thanks!
How were you able to find such a workaround? This seems so unrelated with the issue...

[sheddup]

Yeah! It works! Thanks! How were you able to find such a workaround? This seems so unrelated with the issue...

I basically went through every setting in TC to find the issue.
Also, I believe container number can be set to anything but 'Hide'.

[ghost]

I'm running Firefox 115 ESR (115.4.0 ESR) with Temporary Containers 1.9.2 , just opened about:debugging#/runtime/this-firefox and did not encounter the above mentioned issue. Mode is Automatic and Container Number set to "Reuse available numbers". I've tested with "Hide" and faced no issue as well.
Maybe a compatibility issue with another extension dealing with userContent containers, in particular 'Firefox Multi-Account Containers' (I use none besides TC)? Be noted that in last resort it is always possible to delete the containers.json file in the user's Firefox profile, which gets rebuilt on Firefox restart (take care if using any other container extension which would include your container(s) user data).

[pharaonic-faery]

Hey, thanks for your feedback. I will have a look and test it with ESR.

Maybe a compatibility issue with another extension dealing with userContent containers, in particular 'Firefox Multi-Account Containers' (I use none besides TC)?

The issue occurs even with a clean Firefox profile with no extension. So the problem may come from elsewhere