starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Outline script fails #560

New Issue
Closed
opened 2026-02-04 19:49:29 +03:00 by OVERLORD · 23 comments
OVERLORD commented 2026-02-04 19:49:29 +03:00
Owner
Copy Link

Originally created by @Aloe-recite on GitHub (Feb 26, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Outline

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/outline.sh)"

📝 Provide a clear and concise description of the issue.

Hi, installation fails with this error:

[ERROR] in line 74: exit code 0: while executing command $STD yarn build

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Install script, verbose mode, using advanced settings ONLY to change CT id, root pwd, CT/Gateway IPs.
NO TOUCHING resources like RAM, cores, or any other setting except the ones above.
Debian 12 unprivileged.

❌ Paste the full error output (if available).

[5/5] Building fresh packages...
$ yarn patch-package
yarn run v1.22.22
$ /opt/outline/node_modules/.bin/patch-package
⠇patch-package 7.0.2
Applying patches...
@benrbray/prosemirror-math@0.2.2 ✔
Done in 0.12s.
$ husky install
fatal: not a git repository (or any of the parent directories): .git
husky - git command not found, skipping install
Done in 98.26s.
yarn run v1.22.22
$ yarn clean && yarn vite:build && yarn build:i18n && yarn build:server
$ rimraf build
$ VITE_CJS_IGNORE_WARNING=true vite build
⠏vite v5.4.12 building for production...
node_modules/sonner/dist/index.mjs (1:0) Module level directives cause errors when bundled, "use client" in "node_modules/sonner/dist/index.mjs" was ignored.
node_modules/react-medium-image-zoom/dist/index.js (1:0) Module level directives cause errors when bundled, "use client" in "node_modules/react-medium-image-zoom/dist/index.js" was ignored.
✓ 7216 modules transformed.
⠋(webpackStats plugin) Stats saved to /opt/outline/build/app/webpack-stats.json (567.875KiB)
⠏Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
⠙
[ERROR] in line 74: exit code 0: while executing command $STD yarn build

🖼️ Additional context (optional).

No response

Originally created by @Aloe-recite on GitHub (Feb 26, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Outline ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/outline.sh)" ### 📝 Provide a clear and concise description of the issue. Hi, installation fails with this error: [ERROR] in line 74: exit code 0: while executing command $STD yarn build ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Install script, verbose mode, using advanced settings ONLY to change CT id, root pwd, CT/Gateway IPs. NO TOUCHING resources like RAM, cores, or any other setting except the ones above. Debian 12 unprivileged. ### ❌ Paste the full error output (if available). [5/5] Building fresh packages... $ yarn patch-package yarn run v1.22.22 $ /opt/outline/node_modules/.bin/patch-package ⠇patch-package 7.0.2 Applying patches... @benrbray/prosemirror-math@0.2.2 ✔ Done in 0.12s. $ husky install fatal: not a git repository (or any of the parent directories): .git husky - git command not found, skipping install Done in 98.26s. yarn run v1.22.22 $ yarn clean && yarn vite:build && yarn build:i18n && yarn build:server $ rimraf build $ VITE_CJS_IGNORE_WARNING=true vite build ⠏vite v5.4.12 building for production... node_modules/sonner/dist/index.mjs (1:0) Module level directives cause errors when bundled, "use client" in "node_modules/sonner/dist/index.mjs" was ignored. node_modules/react-medium-image-zoom/dist/index.js (1:0) Module level directives cause errors when bundled, "use client" in "node_modules/react-medium-image-zoom/dist/index.js" was ignored. ✓ 7216 modules transformed. ⠋(webpackStats plugin) Stats saved to /opt/outline/build/app/webpack-stats.json (567.875KiB) ⠏Killed error Command failed with exit code 137. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 137. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. ⠙ [ERROR] in line 74: exit code 0: while executing command $STD yarn build ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 19:49:29 +03:00
OVERLORD commented 2026-02-04 19:49:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 26, 2025):

What for Settings?? You need to fill it. Otherwise i close this issue

@MickLesk commented on GitHub (Feb 26, 2025): What for Settings?? You need to fill it. Otherwise i close this issue
OVERLORD commented 2026-02-04 19:49:44 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 26, 2025):

Image
I can't reproduce this.
If you messed with how many CPU cores and/or ammount of RAM, you're on your own.

@tremor021 commented on GitHub (Feb 26, 2025): ![Image](https://github.com/user-attachments/assets/b5ecfe8d-6689-450d-a824-e06e6d89d061) I can't reproduce this. If you messed with how many CPU cores and/or ammount of RAM, you're on your own.
OVERLORD commented 2026-02-04 19:49:58 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 26, 2025):

same issue here:

🧩 Using Advanced Settings on node pve03
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 101
🏠 Hostname: outline
💾 Disk Size: 12 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 Disable IPv6: no
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;documentation
🔑 Root SSH Access: yes
Warning: No SSH key provided.
🔍 Verbose Mode: no
🚀 Creating a Outline LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-zfs for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 101 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 10.12.22.249 fd00:10:12:22:be24:11ff:fe60:c7f7
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.4
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Set up PostgreSQL Repository
✔️ Installed Node.js
✔️ Set up PostgreSQL
⠹ Setup Outline (Patience)
[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1
root@pve03:~#

@mxlb-dev commented on GitHub (Feb 26, 2025): same issue here: 🧩 Using Advanced Settings on node pve03 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 101 🏠 Hostname: outline 💾 Disk Size: 12 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: no ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;documentation 🔑 Root SSH Access: yes Warning: No SSH key provided. 🔍 Verbose Mode: no 🚀 Creating a Outline LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-zfs for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 10.12.22.249 fd00:10:12:22:be24:11ff:fe60:c7f7 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.121.4 ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Set up Node.js Repository ✔️ Set up PostgreSQL Repository ✔️ Installed Node.js ✔️ Set up PostgreSQL ⠹ Setup Outline (Patience) [ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1 root@pve03:~#
OVERLORD commented 2026-02-04 19:50:02 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Feb 26, 2025):

What for Settings?? You need to fill it. Otherwise i close this issue

I updated my post, sorry but by copying / pasting into the form I lost a bit.
Anyway, I rebuilt it with the same exact settings and this time got

[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1

I re-tried for the third time with the exact same settings and this time it got through...?

@Aloe-recite commented on GitHub (Feb 26, 2025): > What for Settings?? You need to fill it. Otherwise i close this issue I updated my post, sorry but by copying / pasting into the form I lost a bit. Anyway, I rebuilt it with the same exact settings and this time got `[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1` I re-tried for the third time with the exact same settings and this time it got through...?
OVERLORD commented 2026-02-04 19:50:09 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 26, 2025):

Set as Test RAM to 6144 or 8192 and try again

@MickLesk commented on GitHub (Feb 26, 2025): Set as Test RAM to 6144 or 8192 and try again
OVERLORD commented 2026-02-04 19:50:19 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 26, 2025):

Don't think RAM is the issue here. It builds just fine with 4GB.

@tremor021 commented on GitHub (Feb 26, 2025): Don't think RAM is the issue here. It builds just fine with 4GB.
OVERLORD commented 2026-02-04 19:50:27 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 26, 2025):

Now it worked for me, too with adjusted resources:

💾 Disk Size: 16 GB
🧠 CPU Cores: 4
🛠️ RAM Size: 8192 MiB

(Intel N100, if that info is of use) I got it running as docker container already on the same machine with similar specs and no issues. Good luck!

AND HUGE THANK YOU BTW! :)

@mxlb-dev commented on GitHub (Feb 26, 2025): Now it worked for me, too with adjusted resources: 💾 Disk Size: 16 GB 🧠 CPU Cores: 4 🛠️ RAM Size: 8192 MiB (Intel N100, if that info is of use) I got it running as docker container already on the same machine with similar specs and no issues. Good luck! AND HUGE THANK YOU BTW! :)
OVERLORD commented 2026-02-04 19:50:35 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 26, 2025):

All default with Verbose mode:

Image

@tremor021 commented on GitHub (Feb 26, 2025): All default with Verbose mode: ![Image](https://github.com/user-attachments/assets/64ea0854-4aaf-4a22-953a-79336adc1ee8)
OVERLORD commented 2026-02-04 19:50:50 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

Install script completed, but web interface is not loading. Here`s what I found in the postgres logs:

2025-02-26 21:58:46.759 CET [1831] outline@outline FATAL: password authentication failed for user "outline"

@mxlb-dev commented on GitHub (Feb 27, 2025): Install script completed, but web interface is not loading. Here`s what I found in the postgres logs: `2025-02-26 21:58:46.759 CET [1831] outline@outline FATAL: password authentication failed for user "outline"`
OVERLORD commented 2026-02-04 19:50:56 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Feb 27, 2025):

I tried a handful of times, with 4 GB Ram and 6 GB Ram, got 2 errors [ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1 otherwise it worked with both ram settings.
However I'm having troubles configuring authentication despite already having a working bare-metal installation and an env file to copy the needed lines from...but this must be user error ofc

@Aloe-recite commented on GitHub (Feb 27, 2025): I tried a handful of times, with 4 GB Ram and 6 GB Ram, got 2 errors `[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1` otherwise it worked with both ram settings. However I'm having troubles configuring authentication despite already having a working bare-metal installation and an env file to copy the needed lines from...but this must be user error ofc
OVERLORD commented 2026-02-04 19:51:07 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

@Aloe-recite We were in the same boat, but I found the issue.

@MickLesk I noticed the predefined variables were shorter than I had in my other non-community-scripts installation

SECRET_KEY=
UTILS_SECRET=

Once you change both to hex-encoded 32-byte random keys like the note reads, it works. I tested authentication through Slack and a self hosted Authentik.

Here is the corresponding log error:
Feb 27 11:24:57 outline node[365]: {"error":"Invalid key length","level":"error","message":"Failed to encrypt database column (accessToken). The SECRET_KEY environment variable is not the correct length."

The reason why the web interface doesn't load at all, is that it needs at least one working authentication method. If you comment out all methods except one that doesn`t work because it cannot do the encryption, it does not load. Not sure though if this is related to the initial issue that OP and myself had.

I hope this helps.

I suggest you fix the key length.

@mxlb-dev commented on GitHub (Feb 27, 2025): @Aloe-recite We were in the same boat, but I found the issue. @MickLesk I noticed the predefined variables were shorter than I had in my other non-community-scripts installation ``` SECRET_KEY= UTILS_SECRET= ``` Once you change both to hex-encoded 32-byte random keys like the note reads, it works. I tested authentication through Slack and a self hosted Authentik. Here is the corresponding log error: `Feb 27 11:24:57 outline node[365]: {"error":"Invalid key length","level":"error","message":"Failed to encrypt database column (accessToken). The SECRET_KEY environment variable is not the correct length."` The reason why the web interface doesn't load at all, is that it needs at least one _working_ authentication method. If you comment out all methods except one that doesn`t work because it cannot do the encryption, it does not load. Not sure though if this is related to the initial issue that OP and myself had. I hope this helps. I suggest you fix the key length.
OVERLORD commented 2026-02-04 19:51:15 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

update: FYI: I ran into another issue: the first registered user is member and not admin as supposed to. I had to change the role manually in PostreSQL

@mxlb-dev commented on GitHub (Feb 27, 2025): update: FYI: I ran into another issue: the first registered user is member and not admin as supposed to. I had to change the role manually in PostreSQL
OVERLORD commented 2026-02-04 19:51:17 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 27, 2025):

I honestly have no clue what you're doing there that makes you have problem after problem after problem.

I can't reproduce a single problem you have. LXC installs, log is clear of errors, webui comes up after db migration finishes

Image

Offers slack as default auth, but it wont work because you need to configure it, or add any other auth method supported that you want to use

@tremor021 commented on GitHub (Feb 27, 2025): I honestly have no clue what you're doing there that makes you have problem after problem after problem. I can't reproduce a single problem you have. LXC installs, log is clear of errors, webui comes up after db migration finishes ![Image](https://github.com/user-attachments/assets/d65f5940-d12f-408e-a0ac-351293e65eb4) Offers slack as default auth, but it wont work because you need to configure it, or add any other auth method supported that you want to use
OVERLORD commented 2026-02-04 19:51:21 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 27, 2025):

error-log.txt

@tremor021 commented on GitHub (Feb 27, 2025): [error-log.txt](https://github.com/user-attachments/files/19007795/error-log.txt)
OVERLORD commented 2026-02-04 19:51:29 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

@tremor021 Have you tested end-2-end incl authentikation, successful login and can cofirm that your first user is admin? Getting to the default auth screen from your screenshot was no issue for me either. Once I implemented OIDC I got the error mentioned above and corrected the key length as described. Curious what you say :)

@mxlb-dev commented on GitHub (Feb 27, 2025): @tremor021 Have you tested end-2-end incl authentikation, successful login and can cofirm that your first user is admin? Getting to the default auth screen from your screenshot was no issue for me either. Once I implemented OIDC I got the error mentioned above and corrected the key length as described. Curious what you say :)
OVERLORD commented 2026-02-04 19:51:38 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Feb 27, 2025):

@tremor021 Have you tested end-2-end incl authentikation, successful login and can cofirm that your first user is admin? Getting to the default auth screen from your screenshot was no issue for me either. Once I implemented OIDC I got the error mentioned above and corrected the key length as described. Curious what you say :)

I had the same issue, i reached the default auth screen but then OIDC and Slack login doesn't work, whereas they work with the same settings with a bare metal LXC installation I previously had (and still have). Can confirm the different key lenght, although I'm not tech savvy enough to say if that's a issue or not

@Aloe-recite commented on GitHub (Feb 27, 2025): > [@tremor021](https://github.com/tremor021) Have you tested end-2-end incl authentikation, successful login and can cofirm that your first user is admin? Getting to the default auth screen from your screenshot was no issue for me either. Once I implemented OIDC I got the error mentioned above and corrected the key length as described. Curious what you say :) I had the same issue, i reached the default auth screen but then OIDC and Slack login doesn't work, whereas they work with the same settings with a bare metal LXC installation I previously had (and still have). Can confirm the different key lenght, although I'm not tech savvy enough to say if that's a issue or not
OVERLORD commented 2026-02-04 19:51:44 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 27, 2025):

@mxlb-dev I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue.
Try after #2709 merges

@tremor021 commented on GitHub (Feb 27, 2025): @mxlb-dev I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after #2709 merges
OVERLORD commented 2026-02-04 19:51:56 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after #2709 merges

well... my assumption is, that every way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated.

@Aloe-recite let me know if you need any help.

@mxlb-dev commented on GitHub (Feb 27, 2025): > I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after [#2709](https://github.com/community-scripts/ProxmoxVE/pull/2709) merges well... my assumption is, that _every_ way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated. @Aloe-recite let me know if you need any help.
OVERLORD commented 2026-02-04 19:52:06 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Feb 27, 2025):

I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after #2709 merges

well... my assumption is, that every way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated.

@Aloe-recite let me know if you need any help.

Thanks mate, changing the secret key did the trick and now it works, it was as simple as changing the string with a newly generated one and nothing more. Great news. Now I'm stuck with my user being an editor though, and not admin. Care to explain how to correct this? or am I better off running the script from zero? I have no experience when it comes to tinkering with Postgres and the likes :(

@Aloe-recite commented on GitHub (Feb 27, 2025): > > I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after [#2709](https://github.com/community-scripts/ProxmoxVE/pull/2709) merges > > well... my assumption is, that _every_ way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated. > > [@Aloe-recite](https://github.com/Aloe-recite) let me know if you need any help. Thanks mate, changing the secret key did the trick and now it works, it was as simple as changing the string with a newly generated one and nothing more. Great news. Now I'm stuck with my user being an editor though, and not admin. Care to explain how to correct this? or am I better off running the script from zero? I have no experience when it comes to tinkering with Postgres and the likes :(
OVERLORD commented 2026-02-04 19:52:11 +03:00
Author
Owner
Copy Link

@mxlb-dev commented on GitHub (Feb 27, 2025):

I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after #2709 merges

well... my assumption is, that every way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated.
@Aloe-recite let me know if you need any help.

Thanks mate, changing the secret key did the trick and now it works, it was as simple as changing the string with a newly generated one and nothing more. Great news. Now I'm stuck with my user being an editor though, and not admin. Care to explain how to correct this? or am I better off running the script from zero? I have no experience when it comes to tinkering with Postgres and the likes :(

No worries, it`s less scary than you might think ;) I had the same issue.

SSH into your outline LXC or open the console in proxmox. From there log into Postgres DB:
sudo -u postgres psql

then go into outline db:
\c outline;
You should see something that confirms you are connected with outline db with user postgres.

Now check which users are existing (probably only one with role 'member')
SELECT id, name, email, role FROM users;
Note the user ID, something like: 'abcd1234-5678-9abc-def0-1234567890ab'

Set the role to admin (replace id string with yours):
UPDATE users SET role = 'admin' WHERE id = 'abcd1234-5678-9abc-def0-1234567890ab';

run again to see if role has changed to admin:
SELECT id, name, email, role FROM users WHERE id = 'abcd1234-5678-9abc-def0-1234567890ab';

if so, quit the postgres session with:
\q

restart the LXC and that should be it.

@mxlb-dev commented on GitHub (Feb 27, 2025): > > > I say nothing, because i can't test every possible use case of this application. I can patch the script, thats no issue. Try after [#2709](https://github.com/community-scripts/ProxmoxVE/pull/2709) merges > > > > > > well... my assumption is, that _every_ way of authenticating is broken, since none work without correcting the key length. I understand that you cannot test every small usecase, but logging in and getting the correct permissions is pretty much a core feature. Thanks for your swift responses though :) appreciated. > > [@Aloe-recite](https://github.com/Aloe-recite) let me know if you need any help. > > Thanks mate, changing the secret key did the trick and now it works, it was as simple as changing the string with a newly generated one and nothing more. Great news. Now I'm stuck with my user being an editor though, and not admin. Care to explain how to correct this? or am I better off running the script from zero? I have no experience when it comes to tinkering with Postgres and the likes :( No worries, it`s less scary than you might think ;) I had the same issue. SSH into your outline LXC or open the console in proxmox. From there log into Postgres DB: `sudo -u postgres psql` then go into outline db: `\c outline;` You should see something that confirms you are connected with outline db with user postgres. Now check which users are existing (probably only one with role 'member') `SELECT id, name, email, role FROM users;` Note the user ID, something like: 'abcd1234-5678-9abc-def0-1234567890ab' Set the role to admin (replace id string with yours): `UPDATE users SET role = 'admin' WHERE id = 'abcd1234-5678-9abc-def0-1234567890ab';` run again to see if role has changed to admin: `SELECT id, name, email, role FROM users WHERE id = 'abcd1234-5678-9abc-def0-1234567890ab';` if so, quit the postgres session with: `\q` restart the LXC and that should be it.
OVERLORD commented 2026-02-04 19:52:22 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Feb 27, 2025):

@mxlb-dev life saver!! easier than I thought it would be luckily! now the last gripe is that the bare metal install allows to only have OIDC auth, this one does not work without ALSO a slack/google/MS auth set up, even if fake (like "123"). I'll have to look into the documentation, maybe this is some breaking stuff that recently got merged in the last update.
Thanks a lot for your help and to the Community team for the great work and dedication!

@Aloe-recite commented on GitHub (Feb 27, 2025): @mxlb-dev life saver!! easier than I thought it would be luckily! now the last gripe is that the bare metal install allows to only have OIDC auth, this one does not work without ALSO a slack/google/MS auth set up, even if fake (like "123"). I'll have to look into the documentation, maybe this is some breaking stuff that recently got merged in the last update. Thanks a lot for your help and to the Community team for the great work and dedication!
OVERLORD commented 2026-02-04 19:52:27 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Feb 28, 2025):

you can pre-seed admin account via email magic link, you just need to enable SMTP by editing /opt/outline/.env, restart service with systemctl restart outline then run in lxc cd /opt/outline && node build/server/scripts/seed.js my@email.com.

It will generate login link for the email you set as admin

Image

@tremor021 commented on GitHub (Feb 28, 2025): you can pre-seed admin account via email magic link, you just need to enable SMTP by editing `/opt/outline/.env`, restart service with `systemctl restart outline` then run in lxc `cd /opt/outline && node build/server/scripts/seed.js my@email.com`. It will generate login link for the email you set as admin ![Image](https://github.com/user-attachments/assets/3c528259-d955-4958-9c02-1fd49a951852)
OVERLORD commented 2026-02-04 19:52:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 28, 2025):

Can anyone write an Guide for this? I usually only see issues because of that ^^

@MickLesk commented on GitHub (Feb 28, 2025): Can anyone write an Guide for this? I usually only see issues because of that ^^
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#560
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?