ej52/proxmox-scripts

Script bug (?)

endyb66 opened this issue · 12 comments

Environment:
Host: Proxmox 7.4-3
LXC: Debian 11.8

NPM is already running, trying to update with the install-script (alternative using).
Got this error after issuing the command:

~# sh -c "$(wget --no-cache -qO- https://raw.githubusercontent.com/ej52/proxmox/main/install.sh)" -s --app nginx-proxy-manager
-s: 6: Syntax error: "(" unexpected
ej52 commented

Fixed in the latest commit 3a7cf2e

I get another error

/dev/fd/63: line 53: EPS_OS_NAME: unbound variable

ej52 commented

Let's try again, new commit 39b29f7

Okay this time the installation went through. Got some warnings however, I made some screenshots, hope it helps. Oh and I had to manually update the system / packages before using your script, otherwise the script stopped. So I did a

apt-get update && apt-get upgrade && apt-get dist-upgrade && apt-get autoremove && apü-get autoclean

1
2
3

But everything seems to work, great job and thank you!

ej52 commented

@endyb66 Good to hear, those warnings are just nodejs dependancies nothing to worry about.

What terminal/shell are you using? as the logging seems to be weird in the screenshots.

Screenshot 2023-12-05 at 14 35 15

@endyb66 Good to hear, those warnings are just nodejs dependancies nothing to worry about.

What terminal/shell are you using? as the logging seems to be weird in the screenshots.

Screenshot 2023-12-05 at 14 35 15

Alright perfect then!
I'm using putty on windows to connect to my Debian 11.8 Proxmox LXC

dmchmk commented

hi! looks like you also need to fix it in setup.sh -

EPS_OS_NAME=$(os_name)

ej52 commented

hi! looks like you also need to fix it in setup.sh -

EPS_OS_NAME=$(os_name)

Have moved pms_check_os for non CT install instead, as create.sh already does the check

dmchmk commented

oh @ej52 , maybe we have some misunderstanding here, I'm trying to install n-p-m using create.sh as said in the README.md:

bash -c "$(wget --no-cache -qO- https://raw.githubusercontent.com/ej52/proxmox/main/create.sh)" -s --app nginx-proxy-manager --cleanup

and it fails:

изображение

should I avoid installing app directly from the create.sh as it is outdated?

ej52 commented

@megavenik I just ran create.sh using the code from latest commit and that issue is no longer there.
Could be a cache issue :/ You can try again or run the install script in the new container that was created with create.sh

ej52 commented

I see you are actually running create.sh from a old commit, run the script from the main branch

bash -c "$(wget --no-cache -qO- https://raw.githubusercontent.com/ej52/proxmox/main/create.sh)" -s --app nginx-proxy-manager --cleanup

dmchmk commented

yeah, I've tried the last commit mentioned in the #148 (comment) message) but now everything works fine! Thanks a lot for your work on scripts and sorry for disturbing)