Can't access hoobs.local anymore

[chemicalsam]

Nothing in my setup has changed, all of a sudden Hoobs.local UI does not load. Its just white. I have tried multiple browsers and devices. All my devices are still working though.

[askovi]

Please login via SSH and get the HOOBS logs.

1. On MacOS use the Terminal app and type: ssh hoobs@hoobs.local

Type yes to accept the certificate key then press enter. When prompted for password, type hoobsadmin

On Windows, use Putty with the same credentials as above.

2. After successfully logging in, type this: sudo hoobs service log

[witfit2020]

I have the same problem and can't access it with Putty either. I did notice the green network light stopped flashing. Also, when I disconnect the network cable, the WiFi does not activate.

[leehammond]

I have the same problem and when I access the service log I see that the Hoobs service is repeatedly starting and stopping.

This happened after updating to latest version of Hoobs, getting locked out, and then updating to latest version of node as recommended in support threads.

What can I do?

[askovi]

@leehammond
Disable nginx then reboot with the following commands

sudo systemctl disable nginx

sudo setcap CAP_NET_BIND_SERVICE=+eip /usr/local/bin/node

sudo reboot

[leehammond]

@askovi ,

I’ve tried that but I am unable to interrupt the restart processes to disable nginx. How do I disable the service?

[askovi]

press ctrl + c to get out of the logger

[leehammond]

@askovi
Perfect. That did it and can access Hoobs web app. I’m still not able to get home bridge service up and running — do you have any solutions for this?

[askovi]

Click Start Service from the top right menu you have opened there. Then check the logs

[leehammond]

@askovi
Getting the following:

[askovi]

Now update to 3.2.8 from the dashboard and it will fix that issue.

[leehammond]

@askovi
That did it! Thank you for all the help.

[DominicHochberg]

@askovi

same problem, but I can't access anything, as the password is locked. I can't type in the admin password...

[pouilhvladimir]

Please login via SSH and get the HOOBS logs.

1. On MacOS use the Terminal app and type: ssh hoobs@hoobs.local

Type yes to accept the certificate key then press enter. When prompted for password, type hoobsadmin
IT IS NOT LETTING ME TO ENTER NO PASSWORD, SHOWING ME THE KEY CHAIN LOGO
On Windows, use Putty with the same credentials as above.

1. After successfully logging in, type this: sudo hoobs service log

[Bmkenny]

Hi,

I tried updating to the most up to date version of hoobs and now I can’t log in to hoobs.local anymore. I am running hoobs on a rpi and have unplugged it multiple times but can’t get back in. I have a windows machine but am not familiar with the aforementioned system, Putty, and don’t know how to code. Can someone please advise how I can resolve this issue? Thanks in advance!

[askovi]

@Bmkenny

When prompted for password, type hoobsadmin

After successfully logging in, type this: sudo hoobs service log

[Bmkenny]

@askovi Should I download the 32 or 64 bit Putty version?

[askovi]

Depends on your system. Most likely 64bit

[Bmkenny]

@askovi thanks. I think that did it. I'll circle back if any issues persist or new issues surface. Thanks!

[Bmkenny]

Hi @askovi,

I had a power outage recently and tried to replicate the above steps to resolve, but am getting the below error. Can you or someone else please assist?

[askovi]

@Bmkenny That error could indicate a microSD card corruption. This can happen in some rare cases if the HOOBS Box lost power or was improperly shut down by removing the power cable without shutting it down from the top right menu first, while it was writing data to the microSD card. The only fix is to reflash the microSD card. Here are the steps to do that:

You will have to unscrew the 4 screws on the bottom of the HOOBS Box and take the board out then remove the microSD card and plug it into your computer, then follow this guide:
https://support.hoobs.org/docs/5e875c220ab68b0344e872ca

Please open a new issue if you're still having trouble.

[thehotrod]

Askovi or others. I'm having the same problem. Here is my log. Can any one help me? I can't get logged into the web app.

hoobs@hoobs:~ $ sudo hoobs service log at parse (<anonymous>) at readPackage (internal/modules/cjs/loader.js:264:20) at readPackageExports (internal/modules/cjs/loader.js:304:15) at applyExports (internal/modules/cjs/loader.js:446:20) at resolveExports (internal/modules/cjs/loader.js:509:23) at Function.Module._findPath (internal/modules/cjs/loader.js:633:31) at Function.Module._resolveFilename (internal/modules/cjs/loader.js:944:27) at Function.Module._load (internal/modules/cjs/loader.js:840:27) at Module.require (internal/modules/cjs/loader.js:1019:19) at require (internal/modules/cjs/helpers.js:77:18) at Object.<anonymous> (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc32-stream/lib/crc32-stream.js:13:15) at Module._compile (internal/modules/cjs/loader.js:1133:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10) at Module.load (internal/modules/cjs/loader.js:977:32) at Function.Module._load (internal/modules/cjs/loader.js:877:14) at Module.require (internal/modules/cjs/loader.js:1019:19) { path: '/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc-32/package.json' } hoobs.service: Main process exited, code=exited, status=1/FAILURE hoobs.service: Failed with result 'exit-code'. hoobs.service: Service RestartSec=3s expired, scheduling restart. hoobs.service: Scheduled restart job, restart counter is at 1. Stopped HOOBS. Started HOOBS. internal/modules/cjs/loader.js:276 throw e; ^ SyntaxError: Error parsing /usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc-32/package.json: Unexpected token # in JSON at position 4 at parse (<anonymous>) at readPackage (internal/modules/cjs/loader.js:264:20) at readPackageExports (internal/modules/cjs/loader.js:304:15) at applyExports (internal/modules/cjs/loader.js:446:20) at resolveExports (internal/modules/cjs/loader.js:509:23) at Function.Module._findPath (internal/modules/cjs/loader.js:633:31) at Function.Module._resolveFilename (internal/modules/cjs/loader.js:944:27) at Function.Module._load (internal/modules/cjs/loader.js:840:27) at Module.require (internal/modules/cjs/loader.js:1019:19) at require (internal/modules/cjs/helpers.js:77:18) at Object.<anonymous> (/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc32-stream/lib/crc32-stream.js:13:15) at Module._compile (internal/modules/cjs/loader.js:1133:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10) at Module.load (internal/modules/cjs/loader.js:977:32) at Function.Module._load (internal/modules/cjs/loader.js:877:14) at Module.require (internal/modules/cjs/loader.js:1019:19) { path: '/usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc-32/package.json' } hoobs.service: Main process exited, code=exited, status=1/FAILURE hoobs.service: Failed with result 'exit-code'. hoobs.service: Service RestartSec=3s expired, scheduling restart. hoobs.service: Scheduled restart job, restart counter is at 2. Stopped HOOBS. Started HOOBS. internal/modules/cjs/loader.js:276 throw e; ^ SyntaxError: Error parsing /usr/local/lib/node_modules/@hoobs/hoobs/node_modules/crc-32/package.json: Unexpected token # in JSON at position 4

[thehotrod]

Here is a screenshot of the terminal.