HTTP Status Codes in Happeo

This article outlines HTTP status codes you may face in Happeo, what they mean, and what can be done to resolve them.

400 Error

A 400 Bad Request error happens when a server cannot understand a request that’s been made of it. It’s called a 400 error because that’s the HTTP status code that the web server uses to describe that kind of error.

A 400 Bad Request error can happen because there’s a simple error in the request. Perhaps you’ve mistyped a URL and the server can’t return a 404 Error, for some reason. Or maybe your web browser is trying to use an expired or invalid cookie. 

Here are some of the things you can try to resolve this issue: 

1. Perform a hard refresh of the page. Many times the 400 error is temporary, and a simple refresh might do the trick
2. The most common reason for a 400 error is a mistyped URL. If you typed a URL into your address box yourself, it’s possible you mistyped it. Also, check for special symbols in the URL, especially ones that you don’t see in URLs often
3. Clear your browser's cookies and cache. Many websites report a 400 error because the cookies they are reading are either corrupt or too old. Some browser extensions can also change your cookies and cause 400 errors. It’s also possible that your browser has cached a corrupt version of the page you’re trying to open. Please click on the browser you are currently using for instructions on how to clear your cache and your cookies:
   1. Note: When you use a browser, e.g., Chrome, it saves some information from websites in its cache and cookies. Clearing them fixes certain problems, like loading or formatting issues on sites such as Happeo
   2. Google Chrome

   3. Microsoft Edge
   4. Mozilla Firefox
   5. Safari
4. Your computer might be storing outdated DNS records that are causing the errors. Simple flushing of your DNS records might help solve the problem. It’s easy to do, and won’t cause any problems. You can find guides on how to reset your DNS cache on both Windows and macOS
5. Try other websites. If you’ve been trying to open a single website and getting 400 errors, you should try to open other websites to see if the problem persists. If it does, it might be a problem with your computer or networking equipment rather than the website you’re trying to open
6. Restart your computer and other equipment. This solution is hit-and-miss, but restarting your computer and especially your networking equipment (routers, modems) is a common way to get rid of a lot of server errors

If all else fails, please contact our support team so we can further assist you.

Error 400: admin_policy_enforced

Error 400: admin_policy_enforced is not directly related to the Happeo platform, but to the configuration made by the Google Workspace super-admin that restricts access to third-party apps to the Google Workspace data.

To fix it, please follow the steps below (accessing with Google Workspace super admin permissions):

1. Log in to the Google Admin console
2. From the Home page, go to Security
3. Access & Data Controls
4. API Controls
5. App Access Control
6. Manage Third-Party App Access
7. Find the Happeo app and click Change access
8. Choose the Trusted option to allow access to all Google services
9. Click Change

403 Error

Channels

The 403 error "access denied" indicates that you do not have access to the Channel that you're trying to reach.

Unfortunately, we cannot give you access because we are unable to view your environment. Please reach out to the Channel Owner or platform Admin to provide you with access.

If you are unsure who the Channel Owner is, you can navigate to the Channels drop-down menu (the Channel icon at the top corner of the platform that looks like a stack of papers) and click Discover Channels.

From there, you can search the Channel you do not have access to and see who the Owner of the Channel is.

Please note, however, that if the Channel’s discovery settings are set to invite only, you won’t be able to find the Channel through the method provided above.

Pages

The 403 error “access denied” indicates that you do not have access to the Page that you're trying to reach.

Unfortunately, we cannot give you access because we are unable to view your environment. Please reach out to the Page Owner or platform Admin to provide you with access.

Other

When a 403 error like this occurs, there are several steps you can take to resolve the issue, as it can be caused by several factors:

1. Clear Cache & Cookies and try again
2. Try if the same error happens in an incognito browser
3. Check if you are logged into multiple Google Accounts. If so, sign out of them
4. Sign out of Happeo
5. Revoke Happeo Access Permissions in Google
6. Log in to Happeo again (triggering asking for permissions again)
7. Check API

Error 403: emm_app_verification_required

The solution for this issue can be found here.

404 Error

Channels

The 404 error indicates that the Channel you are trying to access is broken or the Channel in question doesn't exist anymore.

Unfortunately, we cannot give you access because we are unable to view your environment. Please reach out to the Channel Owner or platform Admin to provide you with access.

If you are unsure who the Channel Owner is, you can navigate to the Channels drop-down menu (the Channel icon at the top corner of the platform that looks like a stack of papers) and click Discover Channels.

From there, you can search the Channel you do not have access to and see who the Owner of the Channel is.

Please note, however, that if the Channel’s discovery settings are set to invite only, you won’t be able to find the Channel through the method provided above.

Pages

The 404 error indicates that the Page you are trying to access is broken or the Page in question doesn't exist anymore.

Unfortunately, we cannot give you access because we are unable to view your environment. Please reach out to the Page Owner or platform Admin to provide you with access.

500 Error

A 500 Error can occur when there's an internal error, specifically, when a situation arises in the backend and the system doesn’t know how to handle it.

It could be related to:

• A bug in our code
• An unexpected internal state
• Corrupt data in the database

It could also be related to issues with the infrastructure, such as losing connection to the database.

501 Error

We may send this error when you use a non-standard HTTP method.

However, this should practically never happen except during a very thorough penetration testing. Even then, there's a low possibility of the error occurring. 

502 Error

This error occurs when an intermediate server receives a response from a downstream server that it cannot handle.

Our infrastructure involves a lot of intermediate servers and any one of these could temporarily respond with a 502 Error for various reasons.

The intermediate servers start with:

• Google’s global load balancers
• Our API gateway itself
• One or more internal proxies
• Kubernetes service load balancers
• Then some backend services use a proxy internally
• Etc.

503 Error

This generally indicates that the service isn’t configured to handle the load it experiences.

504 Error

This is similar to a 502 Error, in that it’s returned by intermediate servers, and used when the downstream system doesn’t respond in time.

General notes about 5xx Errors

5xx errors signal unexpected server-side conditions, so by their very nature, they are not something an API caller can do much about. It’s more on the side of the service provider to investigate and address the problem.

When you receive a 5xx Error, the error message will detail what you can do to combat the error, such as contacting our support team. 

In case you've developed API clients against our public API, we advise that your development team reads the standards on these codes to know how to handle them.