Affected Versions: Evergreen rel_3_4 / master + Hatch 0.3.2 + Firefox (any)
The Hatch extension for Firefox was never updated to load in .*/eg2/.* URLs, so the Angular client is unable to communicate with Hatch in Firefox. This has not really been that obvious until Hatch 0.3.2 and the associated Evergreen changes in master / rel_3_4 that move all workstation registrations out of the browser's localStorage and into Hatch itself. This causes the current workstation to not be found when retrieving the auth session and then you're dropped at the workstation registration page.
I don't believe that anything needs to be changed in Hatch itself as the extension manifest already lists both /eg/ and /eg2/ URLs, the FF extension just needs to be rebuilt and uploaded to the FF add-on site with the current manifest.
I have confirmed loading the current hatch extension zip into FF as a temporary extension (in the extensions debug view) allows the extension to work for /eg2/ pages.