integration_whiteboard icon indicating copy to clipboard operation
integration_whiteboard copied to clipboard

Workaround Error 403 Access forbidden on Raspberry 4 NC22.2.3 Suggestion to enable parallel Installations.

Open ProfZiebart opened this issue 4 years ago • 6 comments

Ok, this is not really an Issue but more of start of a Hack or Workaround: Maybe a suggestion to enable the use of a parallel installed spacedeck installation??

I tried to get the extension working on a Raspberry Pi 4 with Debian. The spacedeck log in /appdata/spacedeck/spacedeck log shows: spacedeck/spacedeck.log ./spacedeck.nexe.bin: 1: ./spacedeck.nexe.bin:ELF: not found ./spacedeck.nexe.bin: 2: ./spacedeck.nexe.bin: @: not found ./spacedeck.nexe.bin: 3: ./spacedeck.nexe.bin: Syntax error: "(" unexpected

The Binary is not Working at all.

Therefore I installed the spacedeck-open manually on the same machine with a startup script so it runs on 9666 permanently. This leads to the error in the headline: 403 Access forbidden because of a wrong api-token.

To get around that one I logged on to the spacedeck manually, registered a new user and in the "change user account" profile tab inserted an API- Token, e.g. spacedeckapikey. This leads to a new error message as the system now logs on but has a slash too much in the calling URL.

To get around that, I changed /nextcloud/apps/integration_whiteboard/lib/constants.php to define('DEFAULT_SPACEDECK_URL', 'http://localhost:9666'); ( I deleted the last slash)

Now the System shows Spacedeck is working but the first test deck I tried looks very fishy.

Anybody an Idea how to fix it?

ProfZiebart avatar Jan 20 '22 11:01 ProfZiebart

It's a bit tedious, but maybe this will work for you? https://github.com/nextcloud/integration_whiteboard/issues/22#issuecomment-1030878051

teutat3s avatar Feb 09 '22 21:02 teutat3s

Ok I'll try my best but I think I would need help with your steps 0 and 1 as I am nervous about fiddling with npm. It broke too often. Then I'll write down all the commands in a how-to.

ProfZiebart avatar Feb 10 '22 06:02 ProfZiebart

Ok, I'm through with the first run, working on node v10.24.0 and npm 5.8.0. When I add the slash at the End of 9666 I get a 404 errror. If I remove it, I still get the fishy look. Next I moved my own spacedeck to another port to avoid conflicts. Now I get a darn curl error: impossible to load Spacedeck whiteboard "cURL error 7: Failed to connect to localhost port 9666: Verbindungsaufbau abgelehnt (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://localhost:9666/api/spaces"

Next I'm going to upgrade npm and node and retry

ProfZiebart avatar Feb 11 '22 13:02 ProfZiebart

OK now I upgraded to node 17.5.0 with npm 8.5.0, added the export QT_QPA_PLATFORM=offscreen to /usr/bin/nodejs but still I get the libcurl error

ProfZiebart avatar Feb 11 '22 14:02 ProfZiebart

Deactivated and removed the NC Integration just to get a clean start.

ProfZiebart avatar Feb 11 '22 16:02 ProfZiebart

Tried everything. Even a clean restart which killed my server doesn't work. It stays with the curl error even on the nodejs 17.

ProfZiebart avatar Feb 11 '22 20:02 ProfZiebart