Script bug (?) about proxmox-scripts

[ej52]

Fixed in the latest commit 3a7cf2e

[ej52]

Let's try again, new commit 39b29f7

[endyb66]

@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.

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

[megavenik]

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

proxmox-scripts/create.sh

Line 92 in 39b29f7

EPS_OS_NAME=$(os_name)

[megavenik]

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)

[endyb66]

I get another error

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

[endyb66]

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

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

[ej52]

@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.

[ej52]

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

proxmox-scripts/create.sh

Line 92 in 39b29f7

EPS_OS_NAME=$(os_name)

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

[megavenik]

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]

@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]

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