I’ve recently installed Mender 2.0 (production, not demo) on a private server. I’ve encountered an issue while using the UI. The issue is similar to the one that have been mentioned in this post : UI Issue. However, it seems the produced error message is different.
Several seconds after I opened release page of the UI, the page goes blank and there is an error in the console, which says:
Invariant Violation: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=Error%3A%20Response%20timeout%20of%2010000ms%20exceeded&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at main.js:1:850766
at t (main.js:1:850869)
at Gf (main.js:1:896317)
at main.js:1:901020
at S (i/main.js:1:907750)
at main.js:1:932866
at hi (main.js:1:934853)
at ii (main.js:1:935225)
at Ki (main.js:1:941691)
at Li (main.js:1:941085)
Opening this on React Error Decoder, it says : Objects are not valid as a React child. Is it probably a bug or is there something that I haven’t configured properly?
I am not a web developer, so I haven’t fully understood yet how to probe this problem further. However, I can try to look more into the log/details if you can help me with some directions. Thank you.
I’m now seeing the same thing, and I’m seeing it in both Firefox and Chrome, so it’s not a version issue.
Clicking on the error link in the JS Console in Chrome takes me to this page where the error is printed in full:
Objects are not valid as a React child (found: Error: Request has been terminated Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.).
Any help that you can shed on this if you fixed it @alkindirizky would be very much appreciated.
OK, at least part of this was because the storage API’s weren’t starting properly.
This was because the privkey.pem file being generated by my version of certbot/letsencrypt was in the newer ---- BEGIN PRIVATE KEY ---- format rather than the older ---- BEGIN PRIVATE RSA KEY — format.
This was solved by running openssl rsa -in privkey.pem -out privkey.rsa and updating the docker-compose config to read the new file.
I now have an issue whereby the storage service appears to be trying to talk to “localhost”, which obviously isn’t going to work because mender is hosted on a completely different server:
Failed to load resource: net::ERR_CONNECTION_REFUSED
https://localhost/api/management/v1/tenantadm/user/tenant
Thank you for pointing this out - that specific error should be just because of a missing check for our hosted solution (and is checked on page load, which is why it appears on all these pages). It should however not affect the release or devices page, but rather just pollute the console output in the browser devtools.
Is it just the error or does this still prevent the release list from rendering?
@mzedel it still prevents the release list from rendering, however having attempted to access the releases via the API and received a 404 for the given URL, I’m thinking that there’s more at play here than a browser/JS error:
I’m wondering if I’m missing a container somewhere?
Name Command State Ports
---------------------------------------------------------------------------------------------------------
menderproduction_mender-api-gateway_1 /entrypoint.sh Up 0.0.0.0:443->443/tcp
menderproduction_mender-conductor_1 /srv/start_conductor.sh Up 8080/tcp, 8090/tcp
menderproduction_mender-deployments_1 /entrypoint.sh --config /e ... Up 8080/tcp
menderproduction_mender-device-auth_1 /usr/bin/deviceauth --conf ... Up 8080/tcp
menderproduction_mender-elasticsearch_1 /docker-entrypoint.sh elas ... Up 9200/tcp, 9300/tcp
menderproduction_mender-gui_1 /entrypoint.sh nginx Up 80/tcp
menderproduction_mender-inventory_1 /usr/bin/inventory --confi ... Up 8080/tcp
menderproduction_mender-mongo_1 docker-entrypoint.sh mongod Up 27017/tcp
menderproduction_mender-redis_1 /redis/entrypoint.sh Up 6379/tcp
menderproduction_mender-useradm_1 /usr/bin/useradm --config ... Up 8080/tcp
menderproduction_minio_1 /usr/bin/docker-entrypoint ... Up 9000/tcp
menderproduction_storage-proxy_1 /usr/local/openresty/bin/o ... Up 0.0.0.0:9000->9000/tcp
