A page refuses to open, yet the internet connection is working. If the site shows an HTTP status code, that code can narrow the question. Two common access-related responses, 401 and 403, are not interchangeable descriptions of a broken connection.
Read the intended distinction
MDN describes 401 Unauthorized as a request lacking valid authentication credentials. Despite its name, it concerns authentication. 403 Forbidden means the server understood the request but refuses to fulfil it. Signing in again does not necessarily change that refusal.
Check the ordinary access route
Confirm that you are using the correct official address and account. If the resource belongs to an organisation, ask its owner whether your account should have access. Do not repeatedly change URLs or credentials in an attempt to get around a restriction.
Sites can use customised error pages and may not implement status meanings perfectly. Treat the code as a diagnostic clue, then read the accompanying message and the service’s own guidance.
Send a useful support note
Record the time, the page you intended to visit, the exact code and the action immediately before it appeared. Redact tokens or other private values from URLs and screenshots before sharing. A support person needs the problem’s context, not your password.
Compare this with a 404 response. Different codes point toward different questions, even when the visible result is simply that the page is unavailable. A clear report helps distinguish account authentication, permission and missing-resource problems without assuming that clearing everything in the browser will solve them all.