app.co icon indicating copy to clipboard operation
app.co copied to clipboard

App.co not loading

Open pstan26 opened this issue 4 years ago • 8 comments

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

pstan26 avatar Apr 20 '20 15:04 pstan26

@wileyj says this is fixed now

aulneau avatar Apr 20 '20 22:04 aulneau

This appears to be a recurring problem due to the site not reloading automatically after VM's reboots. I've created https://github.com/blockstack/app.co/issues/785 to track its solution.

markmhendrickson avatar Apr 30 '20 13:04 markmhendrickson

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.

diwakergupta avatar May 15 '20 17:05 diwakergupta

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

aulneau avatar May 15 '20 17:05 aulneau

@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?

wileyj avatar May 18 '20 14:05 wileyj

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.

kyranjamie avatar May 18 '20 15:05 kyranjamie

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.

hstove avatar May 18 '20 15:05 hstove

+1 to move it to webflow!!! 🙏

GinaAbrams avatar May 18 '20 15:05 GinaAbrams