Added ETP guidance issues on Codespaces documentation

[thesomewhatyou]

Added guidance through the common issues

Why:

Most people may or may not notice, but ETP blocks Codespaces' ability to connect entirely. And for LibreWolf users like me, this can be pretty frustrating. Eventually, you can add an exception, but if people are new to LibreWolf/Firefox, they won't get the memo fairly quickly. This is why I also added a guide from Mozilla so people can make exceptions + disable it if they want. I do know very angry friends who got so enraged at this issue because they are extremely reliant on Codespaces, but I gave them the solution and it works. I feel like this commit would guide people better.

What's being changed (if available, include any code snippets, screenshots, or gifs):

* Firefox’s Enhanced Tracking Protection (ETP) can cause this error, especially in Strict mode. Add your codespace URL as an exception or turn ETP off.

* LibreWolf, however, does not have the ability to turn off ETP. LibreWolf also forces Strict mode on ETP as well, meaning you must add it as an exception. To add exceptions, go to [Mozilla's guide](https://support.mozilla.org/en-US/kb/manage-enhanced-tracking-protection-exceptions) on how to add exceptions.

Check off the following:

• [X] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• [X] The changes in this PR meet the docs fundamentals that are required for all content.
• [X] All CI checks are passing and the changes look good in the review environment.

[welcome[bot]]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions[bot]]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[thesomewhatyou]

i got paged during this, so my quality is kinda garbage

never push during Friday, you WILL hate yourself

[Sharra-writes]

@thesomewhatyou Thanks for the PR! I'm checking to make sure this is something we feel capable of keeping up with in the future, since edge cases and things that involve specific products that don't belong to us can be tricky to keep up to date in the documentation. This does look useful, though, so I hope we can accept it.

[signorellialain259-beep]

OKY_6JW43nxA5YN

Il lun 20 ott 2025, 21:28 Sharra-writes @.***> ha scritto:

Sharra-writes left a comment (github/docs#40902) https://github.com/github/docs/pull/40902#issuecomment-3423435551

@thesomewhatyou https://github.com/thesomewhatyou Thanks for the PR! I'm checking to make sure this is something we feel capable of keeping up with in the future, since edge cases and things that involve specific products that don't belong to us can be tricky to keep up to date in the documentation. This does look useful, though, so I hope we can accept it.

— Reply to this email directly, view it on GitHub https://github.com/github/docs/pull/40902#issuecomment-3423435551, or unsubscribe https://github.com/notifications/unsubscribe-auth/BWHPTSTETFIGZ7TKAU5GJE33YUZU5AVCNFSM6AAAAACJQ3INAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMRTGQZTKNJVGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[thesomewhatyou]

@Sharra-writes I'm definitely gonna pop in as the updating-the-external-docs ghost, so if you ever see me again, just know I just came here to update external documentation Have a spooky Halloween! I'm gonna be a failed workflow as my costume 😏