Status page has no auto-theme button #2693

Closed
opened 2026-02-28 03:03:41 -05:00 by deekerman · 4 comments
Owner

Originally created by @wc7086 on GitHub (Oct 17, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

image

👟 Reproduction steps

Edit status page

👀 Expected behavior

Allows the status page to automatically select a theme

😓 Actual Behavior

Status page has no auto-theme button

🐻 Uptime-Kuma Version

1.23.3

💻 Operating System and Arch

Windows Server 2012 x64

🌐 Browser

EDGE 118.0.2088.46

🐋 Docker Version

No response

🟩 NodeJS Version

18.18.2

📝 Relevant log output

No response

Originally created by @wc7086 on GitHub (Oct 17, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description ![image](https://github.com/louislam/uptime-kuma/assets/74053663/b08698b8-6640-414f-afa9-b16bdd1eb762) ### 👟 Reproduction steps Edit status page ### 👀 Expected behavior Allows the status page to automatically select a theme ### 😓 Actual Behavior Status page has no auto-theme button ### 🐻 Uptime-Kuma Version 1.23.3 ### 💻 Operating System and Arch Windows Server 2012 x64 ### 🌐 Browser EDGE 118.0.2088.46 ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version 18.18.2 ### 📝 Relevant log output _No response_
deekerman 2026-02-28 03:03:41 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@chakflying commented on GitHub (Oct 17, 2023):

Please check if you are actually running the latest version.

image

@chakflying commented on GitHub (Oct 17, 2023): Please check if you are actually running the latest version. ![image](https://github.com/louislam/uptime-kuma/assets/3271800/01647da1-1472-4766-92a6-338d6233b207)
Author
Owner

@wc7086 commented on GitHub (Oct 17, 2023):

image
Sorry, I typed the wrong system, I am using Windows Server 2012

Installation command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#-non-docker)

# Update your npm
npm install npm@10 -g

git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm run setup

npm install pm2 -g && pm2 install pm2-logrotate

pm2 start server/server.js --name uptime-kuma

Update Command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update#--non-docker)

cd uptime-kuma

# Update from git
git fetch --all
git checkout 1.23.3 --force

npm install --production
npm run download-dist

pm2 restart uptime-kuma
@wc7086 commented on GitHub (Oct 17, 2023): ![image](https://github.com/louislam/uptime-kuma/assets/74053663/56ac7271-38ca-4f6d-952c-ff1275d6051f) Sorry, I typed the wrong system, I am using `Windows Server 2012` Installation command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#-non-docker) ```cmd # Update your npm npm install npm@10 -g git clone https://github.com/louislam/uptime-kuma.git cd uptime-kuma npm run setup npm install pm2 -g && pm2 install pm2-logrotate pm2 start server/server.js --name uptime-kuma ``` Update Command(https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update#--non-docker) ```cmd cd uptime-kuma # Update from git git fetch --all git checkout 1.23.3 --force npm install --production npm run download-dist pm2 restart uptime-kuma ```
Author
Owner

@chakflying commented on GitHub (Oct 17, 2023):

The page should also show your Frontend version if installed correctly.

image

You have most likely updated incorrectly, and the frontend is stuck in an old version. Please follow the instructions in the wiki carefully, make sure there are no errors during the download-dist step before restarting the server.

@chakflying commented on GitHub (Oct 17, 2023): The page should also show your Frontend version if installed correctly. ![image](https://github.com/louislam/uptime-kuma/assets/3271800/acab4b75-7f24-4b13-8251-beb7193b8b97) You have most likely updated incorrectly, and the frontend is stuck in an old version. Please follow the instructions in the [wiki](https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update) carefully, make sure there are no errors during the `download-dist` step before restarting the server.
Author
Owner

@wc7086 commented on GitHub (Oct 17, 2023):

When I repeated the upgrade process and cleared the browser cache, the front-end version showed up correctly. This could be a caching issue. I will revise the content of this issue later.

@wc7086 commented on GitHub (Oct 17, 2023): When I repeated the upgrade process and cleared the browser cache, the front-end version showed up correctly. This could be a caching issue. I will revise the content of this issue later.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2693
No description provided.