Open vstrong-info opened 5 months ago
autonomylab-xyz
commented
5 months ago I've got this too but I'm getting decent earnings on getgrass.io I wonder if the extension has updated and the HTML elements no longer return the right data. I haven't been able to clone and try this locally myself yet
vstrong-info
commented
5 months ago I have another issue on running this container on Synology DS:
Installed! Starting...
Could not start with Manager! Trying to default to manual path...
Could not start with manual path! Exiting...
kgregor98
commented
5 months ago Regarding the first issue, I believe some elements might have changed. Not so long ago they changed the login flow, so I would'nt be surprised.
As for the Synology issue; what kind of processor is your NAS running? The issue with manager not being able to start, is due to ChromeDriver not being available for your CPU architecture, however its the first time I am seeing it fail while trying to get the direct path.
Edit: Does your Grass Dashboard show the browser as connected?
vstrong-info
commented
5 months ago Thank you. Would you be able to check and see if docker can be updated to reflect recent changes?
Synology DS412+ running DSM 6.2.4-25556 Update 7 CPU: INTEL Atom D2700 2 core 2.13 GHz
vstrong-info
commented
5 months ago Regarding the first issue, I believe some elements might have changed. Not so long ago they changed the login flow, so I would'nt be surprised. Edit: Does your Grass Dashboard show the browser as connected? The Grass docker node is working OK. Takes a bit of time to show up on the GRASS dashboard but the container status page is all wrong:
{"connected":false,"epoch_earnings":"","network_quality":false}
vstrong-info
commented
5 months ago @kgregor98 Here are the Synology specs:
Synology DS412+ running DSM 6.2.4-25556 Update 7 CPU: INTEL Atom D2700 2 core 2.13 GHz
Freekers
commented
5 months ago Same issue for me, but earnings seem to accumulate.
LiThaM
commented
5 months ago Same issue to raspberry 3B+
Dreamoffice
commented
5 months ago It looks like it is not connected:
{"connected":false,"epoch_earnings":"462.07K","network_quality":false}Docker logs:
Downloading extension... Downloaded! Installing extension and driver manager... Installed! Starting... Started! Logging in... Logging in... Logging in... Logging in... Logged in! Waiting for connection... Loading connection... Loading connection... Loading connection... Loading connection... Loading connection... Loading connection... Loading connection... Loading connection... Connected! Starting API... * Serving Flask app 'main' * Debug mode: off WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Running on all addresses (0.0.0.0) * Running on http://127.0.0.1:80 * Running on http://172.17.0.3:80 Press CTRL+C to quit
hi could you share your docker config from synology? i have the same problems and i didn t get it running:
autonomylab-xyz
commented
5 months ago My fork of this project solves the connection reporting issue. https://github.com/autonomylab-xyz/grass
Dreamoffice
commented
5 months ago My fork of this project solves the connection reporting issue. https://github.com/autonomylab-xyz/grass
i get this error exec /usr/bin/python: exec format error
It looks like it is not connected:
{"connected":false,"epoch_earnings":"462.07K","network_quality":false}Docker logs: