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 11 Packages Projects Releases 10 Wiki Activity

Outline appears to be broken #1444

New Issue
Closed
opened 2026-02-05 00:49:46 +03:00 by OVERLORD · 21 comments
OVERLORD commented 2026-02-05 00:49:46 +03:00
Owner
Copy Link

Originally created by @dart1235 on GitHub (Aug 12, 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 "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/outline.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

The installation for Outline has succeeded and I can see that nodejs, pgsql etc are all running in the container. However when I try to access the site with the provided URL, the screen is blank. The F12 tools show that the browser downloads the initial page and several JS scripts, etc, and the Outline's favicon is showing on the browser's tab. However the screen is blank.
Could someone please investigate?

🔄 Steps to reproduce the issue.

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/outline.sh)"

Use default settings, then wait and access the HTTP url.

❌ Paste the full error output (if available).

No errors in logs of the service, just indication that web assets are being requested. Also no errors in the browser (F12 console).

🖼️ Additional context (optional).

No response

Originally created by @dart1235 on GitHub (Aug 12, 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 "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/outline.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. The installation for Outline has succeeded and I can see that nodejs, pgsql etc are all running in the container. However when I try to access the site with the provided URL, the screen is blank. The F12 tools show that the browser downloads the initial page and several JS scripts, etc, and the Outline's favicon is showing on the browser's tab. However the screen is blank. Could someone please investigate? ### 🔄 Steps to reproduce the issue. ``` bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/outline.sh)" ``` Use default settings, then wait and access the HTTP url. ### ❌ Paste the full error output (if available). No errors in logs of the service, just indication that web assets are being requested. Also no errors in the browser (F12 console). ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 00:49:46 +03:00
OVERLORD commented 2026-02-05 00:49:51 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 12, 2025):

Did you read this?

https://github.com/community-scripts/ProxmoxVE/discussions/556

@MickLesk commented on GitHub (Aug 12, 2025): Did you read this? https://github.com/community-scripts/ProxmoxVE/discussions/556
OVERLORD commented 2026-02-05 00:49:53 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Aug 12, 2025):

Did you read this?

#556

Hi, I too have the same issues as OP. I have been using Outline since many months with no issues up to v.0.84, the new version 0.86 and 0.86.1 update successfully with the "update" command but then the webpage doesn't load (or, better: it loads, but is completely blank).
Previous version 0,84 works flawlessly.

@Aloe-recite commented on GitHub (Aug 12, 2025): > Did you read this? > > [#556](https://github.com/community-scripts/ProxmoxVE/discussions/556) Hi, I too have the same issues as OP. I have been using Outline since many months with no issues up to v.0.84, the new version 0.86 and 0.86.1 update successfully with the "update" command but then the webpage doesn't load (or, better: it loads, but is completely blank). Previous version 0,84 works flawlessly.
OVERLORD commented 2026-02-05 00:49:55 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 12, 2025):

Any known issue in there repo?

@MickLesk commented on GitHub (Aug 12, 2025): Any known issue in there repo?
OVERLORD commented 2026-02-05 00:49:57 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Aug 12, 2025):

not that I have been able to find / nothing recent tied to updates.

@Aloe-recite commented on GitHub (Aug 12, 2025): not that I have been able to find / nothing recent tied to updates.
OVERLORD commented 2026-02-05 00:50:03 +03:00
Author
Owner
Copy Link

@heretic404 commented on GitHub (Aug 13, 2025):

no issues up to v.0.84, the new version 0.86 and 0.86.1 update successfully with the "update" command but then the webpage doesn't load (or, better: it loads, but is completely blank).

I have exactly same issue. on multiple LXC

@heretic404 commented on GitHub (Aug 13, 2025): > no issues up to v.0.84, the new version 0.86 and 0.86.1 update successfully with the "update" command but then the webpage doesn't load (or, better: it loads, but is completely blank). I have exactly same issue. on multiple LXC
OVERLORD commented 2026-02-05 00:50:07 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 13, 2025):

Multiple outline? 😂

@MickLesk commented on GitHub (Aug 13, 2025): Multiple outline? 😂
OVERLORD commented 2026-02-05 00:50:09 +03:00
Author
Owner
Copy Link

@heretic404 commented on GitHub (Aug 13, 2025):

Multiple outline? 😂

Yes, there are a lot of use cases when there can be multiple deployments, for example, prod and testing environments. It is better to test new integrations and configurations somewhere safe.

@heretic404 commented on GitHub (Aug 13, 2025): > Multiple outline? 😂 Yes, there are a lot of use cases when there can be multiple deployments, for example, prod and testing environments. It is better to test new integrations and configurations somewhere safe.
OVERLORD commented 2026-02-05 00:50:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 13, 2025):

Any logs? because i dont know what i can do here. or report an issue in there repo with all informations? Maybe they have a solution.

@MickLesk commented on GitHub (Aug 13, 2025): Any logs? because i dont know what i can do here. or report an issue in there repo with all informations? Maybe they have a solution.
OVERLORD commented 2026-02-05 00:50:15 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Aug 13, 2025):

I opened a post in they Github bus as much as I can see, their discussion page is not very lively...

@Aloe-recite commented on GitHub (Aug 13, 2025): I opened a post in they Github bus as much as I can see, their discussion page is not very lively...
OVERLORD commented 2026-02-05 00:50:20 +03:00
Author
Owner
Copy Link

@Caelestis94 commented on GitHub (Aug 13, 2025):

I can confirm, outline breaks with the last update 0.86.1, I didn't update to 0.86.0 so I can't say where the break is happening. I checked their github issues, it's been a week or so since those updates an no noise about it on their issues. systemctl status outline.services returns clean, no errors. But the web console gives me an error :

Uncaught Error: Module "path" has been externalized for browser compatibility. Cannot access "path.extname" in client code.  See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
    at Object.get (index.C0rYFSh5.js:912:178)
    at index.C0rYFSh5.js:912:446
    at index.C0rYFSh5.js:2:214
    at index.C0rYFSh5.js:912:1689

I rolled back with my daily backups and it's all good.

@Caelestis94 commented on GitHub (Aug 13, 2025): I can confirm, outline breaks with the last update 0.86.1, I didn't update to 0.86.0 so I can't say where the break is happening. I checked their github issues, it's been a week or so since those updates an no noise about it on their issues. `systemctl status outline.services` returns clean, no errors. But the web console gives me an error : ``` Uncaught Error: Module "path" has been externalized for browser compatibility. Cannot access "path.extname" in client code. See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details. at Object.get (index.C0rYFSh5.js:912:178) at index.C0rYFSh5.js:912:446 at index.C0rYFSh5.js:2:214 at index.C0rYFSh5.js:912:1689 ``` I rolled back with my daily backups and it's all good.
OVERLORD commented 2026-02-05 00:50:24 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 13, 2025):

I will try the docker version to see if it builds/works

@tremor021 commented on GitHub (Aug 13, 2025): I will try the docker version to see if it builds/works
OVERLORD commented 2026-02-05 00:50:26 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 13, 2025):

path is serverside. Looks Like an core issue in this tool

@MickLesk commented on GitHub (Aug 13, 2025): path is serverside. Looks Like an core issue in this tool
OVERLORD commented 2026-02-05 00:50:28 +03:00
Author
Owner
Copy Link

@Caelestis94 commented on GitHub (Aug 13, 2025):

path is serverside. Looks Like an core issue in this tool

I fixed the issue in the script and now its working fine.

    export NODE_ENV=development
    export NODE_OPTIONS="--max-old-space-size=3584"
    $STD yarn install --frozen-lockfile    
    export NODE_ENV=production
    $STD yarn build

switched to export production before the yarn build command and it built and its running fine. If you just switch to production at the top for both the install and build command, the build will fail because of missing dependencies.

@Caelestis94 commented on GitHub (Aug 13, 2025): > path is serverside. Looks Like an core issue in this tool I fixed the issue in the script and now its working fine. ```bash export NODE_ENV=development export NODE_OPTIONS="--max-old-space-size=3584" $STD yarn install --frozen-lockfile export NODE_ENV=production $STD yarn build ``` switched to export production before the yarn build command and it built and its running fine. If you just switch to production at the top for both the install and build command, the build will fail because of missing dependencies.
OVERLORD commented 2026-02-05 00:50:32 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 13, 2025):

Well, that differs from their docs then :) Someone should tell them this....

@tremor021 commented on GitHub (Aug 13, 2025): Well, that differs from their docs then :) Someone should tell them this....
OVERLORD commented 2026-02-05 00:50:36 +03:00
Author
Owner
Copy Link

@tommoor commented on GitHub (Aug 13, 2025):

👋 Outline maintainer, mind pointing me to the incorrect docs?

@tommoor commented on GitHub (Aug 13, 2025): 👋 Outline maintainer, mind pointing me to the incorrect docs?
OVERLORD commented 2026-02-05 00:50:39 +03:00
Author
Owner
Copy Link

@Caelestis94 commented on GitHub (Aug 13, 2025):

I wonder if its because of PR #9523 where they switched from vite to rolldown-vite. Im not too familiar with those tools. @tommoor https://docs.getoutline.com/s/hosting/doc/from-source-BlBxrNzMIP

@Caelestis94 commented on GitHub (Aug 13, 2025): I wonder if its because of PR #9523 where they switched from vite to rolldown-vite. Im not too familiar with those tools. @tommoor https://docs.getoutline.com/s/hosting/doc/from-source-BlBxrNzMIP
OVERLORD commented 2026-02-05 00:50:43 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 13, 2025):

@tommoor like half a year ago, when i made the script, the docs stated that you install and build with NODE_ENV=development set, and it all worked fine until this latest release. So something must have changed. I'm not really familiar with the app itself, i just pieced out everything from dockerfiles and docs available at the time.

The suggestion @Caelestis94 made above fixed the build process, but as it all worked normally before, i think there were some changes introduced that made our script now building improperly...

If you have any suggestions as to what our script should do more, it would be highly appreciated. Maybe its a time for a refactor, but not sure when i can get to it

@tremor021 commented on GitHub (Aug 13, 2025): @tommoor like half a year ago, when i made the script, the docs stated that you install and build with `NODE_ENV=development` set, and it all worked fine until this latest release. So something must have changed. I'm not really familiar with the app itself, i just pieced out everything from dockerfiles and docs available at the time. The suggestion @Caelestis94 made above fixed the build process, but as it all worked normally before, i think there were some changes introduced that made our script now building improperly... If you have any suggestions as to what our script should do more, it would be highly appreciated. Maybe its a time for a refactor, but not sure when i can get to it
OVERLORD commented 2026-02-05 00:50:46 +03:00
Author
Owner
Copy Link

@tommoor commented on GitHub (Aug 13, 2025):

I just updated the instructions, you're not going crazy. The entire build process changed internally in the last version, i don't really have time to investigate how it was working before but the expectation is that you're running production env so this should be a better experience all around once updated – e.g. react isn't rendering everything twice as it does in development ;)

@tommoor commented on GitHub (Aug 13, 2025): I just updated the instructions, you're not going crazy. The entire build process changed internally in the last version, i don't really have time to investigate how it was working before but the expectation is that you're running `production` env so this should be a better experience all around once updated – e.g. react isn't rendering everything twice as it does in development ;)
OVERLORD commented 2026-02-05 00:50:52 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 13, 2025):

Great. I will look into docs some more to see if we need to make any more changes. Thanks for replying.

@tremor021 commented on GitHub (Aug 13, 2025): Great. I will look into docs some more to see if we need to make any more changes. Thanks for replying.
OVERLORD commented 2026-02-05 00:50:56 +03:00
Author
Owner
Copy Link

@Caelestis94 commented on GitHub (Aug 13, 2025):

@tommoor the outline docs have been updated, but if you set prod for both yarn install and yarn build it fails. It needs to export dev for install and prod for build. Tested it right now on my workstation. If you set prod for both steps you get missing deps :

Could not resolve 'browserslist-to-esbuild' in vite.config.ts
Could not resolve 'rollup-plugin-webpack-stats' in vite.config.ts
Could not resolve 'vite-plugin-static-copy' in vite.config.ts

I made a small script

export NODE_ENV=development
yarn install --frozen-lockfile
export NODE_ENV=production
yarn build

and the build worked fine.

@Caelestis94 commented on GitHub (Aug 13, 2025): @tommoor the outline docs have been updated, but if you set prod for both yarn install and yarn build it fails. It needs to export dev for install and prod for build. Tested it right now on my workstation. If you set prod for both steps you get missing deps : `Could not resolve 'browserslist-to-esbuild' in vite.config.ts` `Could not resolve 'rollup-plugin-webpack-stats' in vite.config.ts` `Could not resolve 'vite-plugin-static-copy' in vite.config.ts` I made a small script ```bash export NODE_ENV=development yarn install --frozen-lockfile export NODE_ENV=production yarn build ``` and the build worked fine.
OVERLORD commented 2026-02-05 00:51:00 +03:00
Author
Owner
Copy Link

@tommoor commented on GitHub (Aug 13, 2025):

Ah, that's why it was that way.

@tommoor commented on GitHub (Aug 13, 2025): Ah, that's why it was that way.
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#1444
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?