You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can the issue be reproduced with the latest available release? (y/n) Yes, I am using master, in fact.
Which one is the environment gotify server is running in?
Docker
Linux machine
Windows machine
Do you have an reverse proxy installed in front of gotify server? (Please select None if the problem can be reproduced without the presense of a reverse proxy)
None
Nginx
Apache
Caddy
On which client do you experience problems? (Select as many as you can see)
WebUI
gotify-cli
Android Client
3rd-party API call (Please include your code)
What did you do?
Clone the repository
Install NodeJS and NPM via NVM
Globally install yarn, as it is used in the Makefile
Try make build-js
Also try make build-linux-arm64
What did you expect to see?
A running build process
What did you see instead? (Include screenshots, android logcat/request dumps if possible)
When I tried to do build-js, I get:
root@birb:/srv/gotify# make build-js
(cd ui && yarn build)
yarn run v1.22.19
$ react-scripts build
Creating an optimized production build...
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:69:19)
at Object.createHash (node:crypto:138:10)
at module.exports (/srv/gotify/ui/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:471:10)
at /srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:503:5
at /srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:358:12
at /srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at iterateNormalLoaders (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
at /srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:236:3
at runSyncOrAsync (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:130:11)
at iterateNormalLoaders (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
at Array.<anonymous> (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
at Storage.finished (/srv/gotify/ui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
at /srv/gotify/ui/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
/srv/gotify/ui/node_modules/react-scripts/scripts/build.js:19
throw err;
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:69:19)
at Object.createHash (node:crypto:138:10)
at module.exports (/srv/gotify/ui/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:417:16)
at /srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:452:10
at /srv/gotify/ui/node_modules/webpack/lib/NormalModule.js:323:13
at /srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at /srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:233:18
at context.callback (/srv/gotify/ui/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at /srv/gotify/ui/node_modules/react-scripts/node_modules/babel-loader/lib/index.js:59:103 {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v20.5.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
make: *** [Makefile:127: build-js] Error 1
Something tells me this has to do with the fact that I am running on Ubuntu 22.04 on a Linux server; a VPS rented at Hetzner, part of their recent ARM line.
However, when I tried to do make build-linux-arm64, I get:
root@birb:/srv/gotify# make build-linux-arm64
docker run --rm -v "$PWD/.:/proj" -v "`go env GOPATH`/pkg/mod/.:/go/pkg/mod:ro" -w /proj gotify/build:`cat GO_VERSION`-linux-arm64 go build -mod=readonly -a -installsuffix cgo -ldflags "$LD_FLAGS" -o ./build/gotify-linux-arm64 /proj
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
exec /usr/local/go/bin/go: exec format error
make: *** [Makefile:139: build-linux-arm64] Error 1
So... Do you have any ideas here? I am trying to migrate away from the Docker image since that one doesn't have an ARM image, meaning I couldn't keep using it anymore once i switched servers, unfortunately.
Thank you and kind regards,
Ingwie
The text was updated successfully, but these errors were encountered:
Your first problem is duplicate of #574 , for now you need to export NODE_OPTIONS=--openssl-legacy-provider.
The second problem is you are running an amd64 image for cross compiling to arm on an arm system. If you are building gotify yourself and you have go installed locally you can try build without docker using make build-js && go build -o gotify -ldflags="-s -w -X main.Mode=prod" app.go
Can the issue be reproduced with the latest available release? (y/n) Yes, I am using master, in fact.
Which one is the environment gotify server is running in?
Do you have an reverse proxy installed in front of gotify server? (Please select None if the problem can be reproduced without the presense of a reverse proxy)
On which client do you experience problems? (Select as many as you can see)
What did you do?
make build-js
make build-linux-arm64
What did you expect to see?
A running build process
What did you see instead? (Include screenshots, android logcat/request dumps if possible)
When I tried to do
build-js
, I get:Something tells me this has to do with the fact that I am running on Ubuntu 22.04 on a Linux server; a VPS rented at Hetzner, part of their recent ARM line.
However, when I tried to do
make build-linux-arm64
, I get:So... Do you have any ideas here? I am trying to migrate away from the Docker image since that one doesn't have an ARM image, meaning I couldn't keep using it anymore once i switched servers, unfortunately.
Thank you and kind regards,
Ingwie
The text was updated successfully, but these errors were encountered: