question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to load resource: the server responded with a status of 504 (Gateway Timeout)

See original GitHub issue

I’m submitting a…


[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Angular service worker application throws following error

Failed to load resource: the server responded with a status of 504 (Gateway Timeout) ng new my-project --service-worker

Expected behavior

It should not throw any exceptions

Minimal reproduction of the problem with instructions

ng new my-project --service-worker ng build --prod cd dist http-server -p 8080 Even with IIS host i can see the same issue.

What is the motivation / use case for changing the behavior?

Environment


Angular version: 5.2.6


Browser:
- [x] Chrome (desktop) version 64.0.3282.167
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: v9.5.0  
- Platform:  Windows 

Others:

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:6
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
gkalpakcommented, Mar 26, 2018

@akilmakda, the error message (which comes from the browser, not @angular/service-worker) explains why it is failing. I don’t think this is related to Angular’s ServiceWorker.

(In any case, this issue is not the place to discuss unrelated problems. If you still think there is an issue with @angular/service-worker please open a new isue.)

0reactions
angular-automatic-lock-bot[bot]commented, Sep 13, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Failed to load resource: the server responded with a status ...
In web console log Failed to load resource: the server responded with a status of 504 (Gateway Timeout), the above error prints. If...
Read more >
The Quick & Easy Guide to Fixing 504 Gateway Timeout ...
A 504 Gateway Timeout Error means your web server didn't receive a timely response from another server upstream when it attempted to load...
Read more >
How to Fix the 504 Gateway Timeout Error on Your Site
A 504 Gateway Timeout error indicates that the web server is waiting too long to respond from another server and “timing out.” There...
Read more >
Here's how to fix a 504 Gateway Timeout error
The 504 Gateway Timeout error is an HTTP status code that means that one server didn't receive a timely response from another server...
Read more >
504 Gateway Timeout - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 504 Gateway Timeout server error response code indicates that the server, while acting as a gateway ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found