HTTP 504 error on pages: .Changed pages never loading

The whole DevHub loads fine for me, except the pages for the Changed events of different value objects

https://developer.roblox.com/api-reference/event/Vector3Value/Changed
https://developer.roblox.com/api-reference/event/NumberValue/Changed
https://developer.roblox.com/api-reference/event/ObjectValue/Changed
https://developer.roblox.com/api-reference/event/StringValue/Changed
https://developer.roblox.com/api-reference/event/Color3Value/Changed
and more. If you wait long enough you;ll get a 504 Error from CloudFront, along with this message

"If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by following steps in the CloudFront documentation (https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html). "

Edit: Also getting this error for the following page:
https://developer.roblox.com/api-reference/datatype/PathWaypoint

6 Likes

I’m getting the error on just about every page under the api-reference category as well.

Getting this as well, but not only under /api-reference. There are random pages under /articles and /resources that do the same thing. Seems to be an issue with the entire website.

2 Likes

Getting this too. GroupService page doesn’t load.

Edit: Fixed link since I copied the wrong link. Basically I just erased the /GetGroupsAsync part from url and copied that url thinking it would go to the GroupService page.

1 Like

Pretty sure the servers are down or something along those lines.

im also getting this on all developer hub pages

504 ERROR

The request could not be satisfied.

CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
If you received this error while trying to use an app or access a website, please contact the provider or website owner for assistance.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by following steps in the CloudFront documentation (https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html).

Generated by cloudfront (CloudFront) Request ID: 9Gi3fVsj5mq_CfrxITnIJ6kXaX_xYEo6RUbwBYXLhYQQtSey-Wmc6w==

Can also say nothing is loading on my end within api-reference. Tried loading HttpService but no luck sadly.

It’s now listing an NGINX error.

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.

cc @UristMcSparks

Can confirm it for every api-reference page.

1 Like

HTTP 504 errors spotted; I can confirm.

I am trying to access some API references for some project of mine. Unfortunately, the pages seem to never load; something must have failed at the host’s end(server).

Got this error too.

I got the same error on https://developer.roblox.com/api-reference/class/RunService

Here is the error:

504 ERROR

The request could not be satisfied.

CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection.
If you received this error while trying to use an app or access a website, please contact the provider or website owner for assistance.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by following steps in the CloudFront documentation (https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/http-504-gateway-timeout.html).

Generated by cloudfront (CloudFront) Request ID: W9myWnhzVyTMYpGG5FzhrJmGYFoxRU_-gSPQ4-AeHqIF_Mlr2zzuIQ==

Seems like its fixed now.

1 Like

Hey there! Just a heads up that this page loads successfully (as of now). The link you sent attempts to visit a function page for GroupService, which is actually a class. Here is a valid link to the page: GroupService

1 Like

Hey everyone,

Thanks for raising this issue. The Developer Hub is back online and we are actively investigating the root cause.

2 Likes

Hey everyone,

We have pinpointed the root of the issue and implemented a fix. You should no longer see errors when visiting the site.

Thanks for your patience!

1 Like