Your browser saves copies of the pages, images and files it has already downloaded from Halaxy so they load faster the next time you visit. When Halaxy is updated, your browser sometimes keeps using an older copy, so a page shows out-of-date information, a screen stops responding, or a new feature does not appear in your account.
Refreshing the page or clearing your browser cache removes those older copies and loads the current version of Halaxy.
Clear your cache and cookies when Halaxy behaves in one of these ways:
-
A page shows out-of-date information, such as a fee, name or setting you have already changed.
-
A screen or pop-up does not open or stops responding.
-
A feature announced in a Halaxy update does not appear in your account.
-
Buttons, menus or text appear in the wrong place on the page.
-
You are signed out repeatedly, or a message tells you your session has expired.
Important
Clearing cookies signs you out of Halaxy and every other website you are signed in to on that browser. If you use two-factor authentication, your device is no longer remembered, and you are asked for a code the next time you sign in. Have your sign-in details ready before you start.
A hard refresh reloads the page and ignores the copy your browser has stored. It applies only to the page you are on and does not sign you out of Halaxy.
On the Halaxy page that is not displaying correctly, press the keys for your browser:
|
Browser |
Windows |
Mac |
|---|---|---|
|
Chrome, Edge and Firefox |
Ctrl + F5 |
Command + Shift + R |
|
Safari |
Not applicable |
Option + Command + R |
If the page still displays incorrectly, follow the steps for your browser below.
Tip
To check whether the cache is the cause, open Halaxy in a private or incognito window. If the page displays correctly there, clearing your cache will resolve it in your normal window.
Open the section for the browser you use.
-
Google Chrome
-
On the top right, click the three dots icon.
-
Click Delete browsing data.
-
In the pop-up:
-
Next to Time range, select All time from the dropdown.
-
Tick the Cached images and files and Cookies and other site data checkboxes. Note: Clearing cookies signs you out of the websites you are signed in to on this browser.
-
Click Delete data.
-
-
Close and reopen Chrome, then sign in to Halaxy.
-
-
Safari
Safari does not have separate options for cached files and cookies. These steps remove both for Halaxy and leave every other website untouched.
-
On the menu bar, click Safari > Settings. In older versions of Safari, click Safari > Preferences.
-
Click the Privacy tab.
-
Click Manage Website Data.
-
In the search field, enter "Halaxy".
-
Select the Halaxy entries, then click Remove. This removes the cookies as well, so you are signed out of Halaxy.
-
Click Done, then close and reopen Safari and sign in to Halaxy.
-
-
Microsoft Edge
-
On the top right, click the three dots icon.
-
Click Delete browsing data.
-
In the pop-up:
-
Under Time range, select All time from the dropdown.
-
Tick the Cached images and files and Cookies and other site data checkboxes. Note: Clearing cookies signs you out of the websites you are signed in to on this browser.Ticking cookies signs you out of the websites you are signed in to on this browser.
-
Click Clear now.
-
-
Close and reopen Edge, then sign in to Halaxy.
-
-
Mozilla Firefox
-
On the top right, click the three lines icon.
-
Click Settings > Privacy & Security.
-
Under Browsing data, click Clear browsing data.
-
In the pop-up:
-
Next to When, select Everything from the dropdown.
-
Tick the Cookies and site data and Temporary cached files and pages checkboxes. Note: Clearing cookies signs you out of the websites you are signed in to on this browser.
-
Click Clear.
-
-
Close and reopen Firefox, then sign in to Halaxy.
-
-
Sign out of Halaxy and sign back in.
-
Open Halaxy in a different browser to check whether the problem follows you.
-
Restart your router and computer.
If Halaxy still does not display correctly, contact Halaxy support. Include the page you were on, what you expected to see, and a screenshot of the problem.
Updated