Skip to content
This repository was archived by the owner on Jan 6, 2023. It is now read-only.

App.co not loading #783

Open
pstan26 opened this issue Apr 20, 2020 · 8 comments
Open

App.co not loading #783

pstan26 opened this issue Apr 20, 2020 · 8 comments
Labels
bug Something isn't working

Comments

@pstan26
Copy link

pstan26 commented Apr 20, 2020

Describe the bug
tried to got to app.co and it loads a mostly blank screen.

Screen Shot 2020-04-20 at 11 29 30 AM

To Reproduce
Steps to reproduce the behavior:

  1. Go to app.cp
  2. See error

Desktop (please complete the following information):

  • Chrome
  • Version 79.0.3945.130

Smartphone (please complete the following information):

  • iPhone7
  • Browser Chrome
@aulneau aulneau assigned hstove and unassigned hstove and aulneau Apr 20, 2020
@aulneau
Copy link
Contributor

aulneau commented Apr 20, 2020

@wileyj says this is fixed now

@markmhendrickson markmhendrickson added the bug Something isn't working label Apr 30, 2020
@markmhendrickson
Copy link
Contributor

markmhendrickson commented Apr 30, 2020

This appears to be a recurring problem due to the site not reloading automatically after VM's reboots. I've created #785 to track its solution.

@diwakergupta
Copy link

I don't think #785 will fix this. Right now we assume app.co is a fully stateless service and if so, daily restarts shouldn't have any impact. Implementing the health-check will make the above process a bit nicer, but not much beyond that.

I suspect this is a nextjs issue and would like @hstove or @kyranjamie to spend some time confirming the root cause here.

@aulneau
Copy link
Contributor

aulneau commented May 15, 2020

I would think this error is a caching error. Typically when there are assets that can't be found via /_next/..., it's due to a build hash not matching up with what is found locally. This could be helpful: https://github.com/nexdrew/next-build-id

@wileyj
Copy link
Collaborator

wileyj commented May 18, 2020

@aulneau in this case though, that would require the site to be running multiple builds, which currently is not the case. Sticky sessions are also enabled at the load balancer, so a request wouldn't be bouncing between different instances of the running site.
is there a way to check this build hash from the host?

@kyranjamie
Copy link
Contributor

I've made PRs addressing #785 and #788. Need @hstove / @aulneau's input on whether we need to tackle #786, or whether we can find another solution, as I believe it'd require some serious refactoring.

@hstove
Copy link
Contributor

hstove commented May 18, 2020

Honestly, I think the best approach here is to finalize the migration to webflow. Refactoring to reduce page load size would take at least the same amount of work (probably more). Moving to webflow has more potential for the future, in my opinion.

@GinaAbrams
Copy link

+1 to move it to webflow!!! 🙏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants