standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it @echarles | @ericsnekbytes | @github-actions | @jtpio | @ofek | @RRosio 5.6 6.4.12 (Full Changelog • Address security advisory GHSA-v7vq-3x77-87vg 5.7 6.4.11 (Full Changelog) 5.7.1 Bugs fixed • Update further

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it @echarles | @ericsnekbytes | @github-actions | @jtpio | @ofek | @RRosio 5.5 6.4.12 (Full Changelog • Address security advisory GHSA-v7vq-3x77-87vg 5.6 6.4.11 (Full Changelog) 64 Chapter 5. Changelog Jupyter

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it @echarles | @ericsnekbytes | @github-actions | @jtpio | @ofek | @RRosio 5.7 6.4.12 (Full Changelog • Address security advisory GHSA-v7vq-3x77-87vg 5.8 6.4.11 (Full Changelog) 5.8.1 Bugs fixed • Update further

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it @echarles | @ericsnekbytes | @github-actions | @jtpio | @ofek | @RRosio 5.9 6.4.12 (Full Changelog • Address security advisory GHSA-v7vq-3x77-87vg 5.10 6.4.11 (Full Changelog) 5.10.1 Bugs fixed • Update

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it @echarles | @ericsnekbytes | @github-actions | @jtpio | @ofek | @RRosio 5.8 6.4.12 (Full Changelog • Address security advisory GHSA-v7vq-3x77-87vg 5.9 6.4.11 (Full Changelog) 5.9.1 Bugs fixed • Update further

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it when websockets are closed. • Launch the browser with a local file which redirects to the server address including the authentication token. This prevents another logged-in user from stealing the token

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it when websockets are closed. • Launch the browser with a local file which redirects to the server address including the authentication token. This prevents another logged-in user from stealing the token

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it when websockets are closed. • Launch the browser with a local file which redirects to the server address including the authentication token. This prevents another logged-in user from stealing the token

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it when websockets are closed. • Launch the browser with a local file which redirects to the server address including the authentication token. This prevents another logged-in user from stealing the token

standard install instructions, Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. try turning it off temporarily, and look in the settings for a more long-term solution. • In the address bar, try changing between localhost and 127.0.0.1. They should be the same, but in some cases it when websockets are closed. • Launch the browser with a local file which redirects to the server address including the authentication token. This prevents another logged-in user from stealing the token