-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS TypeError in OZentry, when evaluating e.length #827
Comments
I'm fairly sure this is what happens if an attempt to fetch node details returns no results (read: the DB is empty). Fairly sure it's 'nowt to do with certs, but it should certainly be failing more gracefully. |
Thanks. This is running from the production DB, so I would hope it wasn't empty (and indeed it seems not to be, when I log directly into the database) |
Yup, if you look at the network tab the |
Ah, maybe it's because it's asking via https then? I can't actually seem to visit the http:// version of the site: it switches me back to https even if I clear the website details. So I can't test it until we have proper certs for the new site |
It's not related to the self-signed certs, there's server-side upset: With new onezoom:
With old onezoom (i.e. /etc/hosts bodge commented out):
The |
Yup. The problem will be somewhere behind this: Lines 87 to 88 in fb96f14
My bet would be it complaining about a lack of |
Ah, thanks for the triage. The |
Ah:
|
So just a matter of turning on |
Yep, I tried that, but for some reason it's not doing the migrations correctly, so I simply copied the table definition from beta using raw SQL. It seems to be working. |
When testing the "new" prod, I'm getting the following error. Perhaps the API is failing because of not having a valid cert. Nevertheless, I suspect it should be failing more gracefully?
The text was updated successfully, but these errors were encountered: