Closed jcohenho closed 4 years ago
Thanks for the feedback.
I'm not able to replicate your issue on my end when performing a clone of the master branch and running npm install
as per the guidance in the CANcloud documentation.
Can you clarify the steps to reproduce your issue, incl. your system details?
As for the issue of logging in, have you tried our hosted link? https://canlogger.csselectronics.com/cancloud/#/login
I'd assume this is not related to the installation of CANcloud, but rather something related to the login details you use. In case you can't log in via the hosted link above, please send your login details via our contact form and we'll review: https://www.csselectronics.com/screen/page/can-bus-logger-contact
I cloned the repo from master branch and ran npm install
using node v13.2.0. I'm on Mac OS High Sierra Version 10.13.6.
I was able to successfully login on my local install and on your link after using the correct admin login credentials. It looks like you aren't able to login with credentials that are restricted to using S3FullAccess Policies, only permissions with administrator access works. It would be nice to be able to login with S3FullAccess policy-enabled accounts to limit the scope of access.
Hi again,
We've not done testing yet of installing CANcloud via npm install
on Mac, so that might be related.
Note that if you're not in need of modifying the source code, you can alternatively host your own version by getting the compiled versions under our Releases section and extracting those to your web server - it'll be a lot faster and easier.
As for the access via restricted accounts, this should be possible similarly to how you'd normally use these. As an example, we have a user set up with limited access which we use as our "CANcloud demo" user, see the CANcloud demo link.
I'm not sure if you're using MinIO or AWS S3?
I'm using AWS S3. Please ignore my comment about limited access, I was finally able to login on an S3FullAccess account.
I'll host my own web app using the compiled versions, thank you!
Ok thanks for the update - I'll close this, we'll review the Mac aspect down-the-line.
I'm trying a brand new installation of this app and
npm install
fails:The second issue is even when ignoring the failed install and running
npm start
I enter in my AWS S3 credentials, and I get a bad request with valid credentials for an existing bucket:400 Bad Request https://existing-bucket-name.s3.amazonaws.com/?location