safari can't open github

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Mac Mini M1 Cannot Access GitHub

I asked this before but can no longer find the thread...

My M1 Mac Mini refuses to load GitHub unless I am connected to a VPN.

If I'm not routed through my ProtonVPN the website won't load but it loads successfully when I am connected through the VPN.

I've tried deleting Proton just in case there was some sort of configuration blocking something (using CleanMyMac X) but no change.

I've tried booting in safe mode an no luck there either.

I've had this issue for quite a while now and it's really becoming a pain. Would be grateful of any help.

Mac mini, macOS 13.0

Posted on Jun 23, 2022 11:23 AM

Posted on Jun 23, 2022 11:46 AM

Ok I solved it....

I cleared cookies and cache from Safari

Restarted into Safe Mode and GitHub loaded fine

I then restarted into normal mode and GitHub is loading fine there too.

Not sure if clearing the cache in Safari was a the true fix as I had not been able to load GitHub in Firefox either, previously.

Maybe this will help someone sometime.

Similar questions

• Content caching error Mac mini (M1, 2020), 12.4 Issue: -Content Caching is not working -Error: Content Caching is temporarily unavailable -RegistrationError: REQUEST_DENIED and RegistrationResponseCode: 403. -Using the cache util command line options, I can get it to a state where content caching is activated, but the registration with Apple portion appears to be failing. Steps taken: -Connected via ethernet -Same issue on wifi -Mac has been set up as new out of box, no vpn, anti virus -Same issue on test user -Turn on/off content caching multiple times How did you get your content caching to work? 827 1
• System Preferences Can't Connect to internet System Preferences can't connect to interenet. This blocks me from adding google accounts and updating my mac. There is no other problem with the internet, just in the System Preferences. I think this is maybe because my mac is pretty old, and I cannot run a later OS than Catalina, and maybe this is what's causing the problem, but I'm not sure. Would love to fix this problem, see attached screenshots. Thank You 409 1
• Older MacOS Download Links Not Working Hello, I have been trying to update my mid-2013 mac book air. I have been following this support page to get the updates. https://support.apple.com/en-us/HT211683 I've gotten Sierra running with no issues, but anything newer won't load. None of the "Use Safari to download macOS on your Mac" download links work. I tried all of them (Big Sur, Catalina, Mojave, and High Sierra) in safari, but I got blank web pages for every one. I tried restarting the computer, having the app store closed, having the app store open, loading it in safe mode. Nothing worked. The link to Monterey loads up just fine on the store, and through the safari redirect, but it appears to be incompatible with my mid-2013 air. According to the same support page, it lists Big Sur, Catalina, Mojave, and High Sierra as compatible with my computer. Is there anyway to access these versions? 500 2

Loading page content

Page content loaded

Jun 23, 2022 11:46 AM in response to spcurtis81

If Safari doesn't open a page or work as expected on your Mac

If Safari doesn't load a webpage, stops responding, quits unexpectedly, or otherwise doesn't work as expected, these solutions might help.

These solutions are for issues that can affect Safari on Mac, including issues such as these:

A webpage is blank, doesn't load all of its content, or otherwise doesn't work as expected.

You can't sign in to a webpage, despite using the correct sign-in information.

A webpage asks you to remove or reset cookies.

Safari slows down, stops responding, or quits unexpectedly.

Reload the page

From the menu bar in Safari, choose View > Reload Page. Or press Command-R.

If Safari doesn't reload the page, quit Safari, then try again. If Safari doesn't quit, you can press Option-Command-Esc to force Safari to quit .

If Safari automatically reopens unwanted pages, quit Safari, then press and hold the Shift key while opening Safari. Learn how to control which windows Safari automatically reopens .

Install software updates and restart

Update macOS , which can include updates for Safari. If your Mac didn't restart automatically, choose Apple menu  > Restart. Some important background updates take effect only after restarting.

Check Safari extensions

If you installed any Safari extensions, turn extensions off. From the menu bar in Safari, choose Safari > Settings (or Preferences). Click Extensions, then deselect each extension to turn it off. Learn more about Safari extensions .

If you find that an extension is causing the issue, make sure that the extension is up to date.

Test with a private window

A website can store cookies, caches, and other data on your Mac, and issues with that data can affect your use of the website. To prevent the website from using that data, view it in a private window: From the menu bar in Safari, choose File > New Private Window, or press Shift-Command-N.

If that works, use the following steps to remove the website's data, including its caches and cookies. The website can then create new data as needed. If it's a website that you sign in to, make sure that you know your sign-in information before continuing.

Choose Safari > Settings (or Preferences), then click Privacy.

Click Manage Website Data.

Select the affected website from the list shown.

Click Remove.

Click Done.

Open the website again in a non-private browser window.

Check Safari settings

The webpage might not be compatible with one or more browser settings, which you can turn on or off as needed. From the menu bar in Safari, choose Safari > Settings (or Preferences). Then click Websites, Privacy, or Security to access these settings:

Privacy settings . These settings apply to all websites. For example, a website might require that you allow cross-site tracking, show your IP address, or allow cookies.

Security settings . These settings apply to all websites. For example, a website might require that you enable JavaScript.

Websites settings . These settings can be configured for specific websites. For example, a website might require that you allow pop-up windows, allow downloads, allow access to your camera or microphone, or turn off content blockers.

Check iCloud Private Relay

If you subscribe to iCloud+ and are using its Private Relay feature, try reloading the page without Private Relay: From the menu bar in Safari, choose View > Reload and Show IP Address. This menu item appears only when Private Relay is turned on for your network. Learn more about iCloud Private Relay .

Check VPN or other security software

If you installed VPN or other software that monitors or interacts with your network connections, that software could affect your use of the website or the internet. Learn about network issues related to VPN and other software .

Check network settings

Certain network settings, such as custom proxy settings or custom DNS settings , can affect access to content on the internet. Even if you haven't changed these or other network settings yourself, you might have installed software that changed them for you.

To find out whether the issue is with the network settings on your Mac, try viewing the page from a different web browser or different device on the same network. Or reset your network settings by setting up a new network location on your Mac.

If the issue affects other devices and web browsers on the same network, the issue is probably with the website, and you should contact the website developer for help.

If the issue continues to affect only a particular webpage, contact the website developer for help.

Learn how to block pop-up ads and windows in Safari .

Learn what to do if your iCloud or Safari bookmarks aren't syncing .

Related topics

Explore Apple Support Community

Find what’s been asked and answered by Apple customers.

Troubleshooting your connection to GitHub Codespaces

Troubleshooting help for connecting to GitHub Codespaces.

In this article

503 codespace service unavailable.

Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a 503 service unavailable error.

• If a Start button is shown in Visual Studio Code or in your browser window, click Start to reconnect to the codespace.
• Reset your codespace by reloading the window. From the Command Palette in Visual Studio Code, click Developer: Reload Window .

Browser cannot connect

Sometimes you may not be able to access a codespace from your browser. If this happens, go to https://github.com/codespaces and try connecting to the codespace from that page.

• If the codespace is not listed on that page, check that you are the owner of the codespace you are trying to connect to. You can only open a codespace that you created.
• If the codespace is listed but you cannot connect from that page, check whether you can connect using a different browser.

Diagnose by error message

"oh no, it looks like you are offline".

Check that you have a stable internet connection and that your company network is not blocking the connection. If possible, check logging for rejected connections on your device.

If you see rejected connections, make sure the domains documented by the /meta REST API endpoint are not blocked by your firewall. For more information, see " REST API endpoints for meta data ."

To get the list of domains required by GitHub Codespaces, execute the following command using GitHub CLI:

gh api meta | jq .domains.codespaces

"We are having trouble fetching your codespace information"

This is a transitional error. Wait for a few minutes and try again.

"We were unable to authenticate your connection"

This indicates that something went wrong with authentication. Try clearing up your local storage and cookies and try again.

If you still can't connect and the message you're seeing isn't in this list, check the service availability of Codespaces at githubstatus.com . If the Codespaces service is available, you may need to contact support. For more information, see " Working with support for GitHub Codespaces ."

Unable to connect to your codespace in JupyterLab

To be able to use a codespace in JupyterLab, you must ensure that your codespace has it installed. The default dev container image that's used by GitHub Codespaces includes JupyterLab, but if you have customized your dev container configuration you will have to manually install JupyterLab.

If your codespace uses a Debian-based image, you can install JupyterLab in the dev container by adding the python feature to your devcontainer.json file, with the installJupyterlab option set to true . Otherwise, install it directly in your Dockerfile. For installation instructions, see " Installation " in the JupyterLab documentation.

For more information about the python feature, see the README page in the devcontainers/features repository . For more information about the devcontainer.json file and the Dockerfile, see " Introduction to dev containers ."

If you still cannot connect, you may need to contact support. For more information, see " Working with support for GitHub Codespaces ."

GitHub Codespaces extension for Visual Studio Code cannot connect

If you cannot connect to a codespace from Visual Studio Code desktop, use the following troubleshooting steps.

• In Visual Studio Code, display the "Extensions" tab.
• Select the GitHub Codespaces extension to display the extension's overview page.
• If an update is available, a button is shown, click Update to X.X.X to upgrade to the latest version.
• Check whether you are using the stable build of Visual Studio Code or the Visual Studio Code Insiders release (nightly updates). If you are using the insiders release, try installing the stable build .
• Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device.

The codespace has latency issues

If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can manually set your GitHub Codespaces region .