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

habitica script #584

New Issue
Closed
opened 2026-02-04 20:07:48 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 20:07:48 +03:00
Owner
Copy Link

Originally created by @adavi1995 on GitHub (Mar 4, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Habitica LXC

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

The one provided

📝 Provide a clear and concise description of the issue.

Currently the command to install the script is broken - at least it was for me. This script is not finished for anyone who wants to reverse proxy it/external access or access with the app unless I am misunderstanding something, but after 2 days of struggling, and trying different things I have found that there are more steps to follow - cd /opt/habitica/website/client
run the commands
'npm install'
'npm run build' - this one takes a hot minute.
my config.json I changed the base_url to my subdomain e.g. https://habitica.domain.com
here is the link where I have found the relevant commands
https://github.com/HabitRPG/habitica/tree/develop/website/client
I reverse proxied my ip with port 3000 (server port not the client)

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

To reproduce the issues I had, just install the script and try reverse proxying - I kept getting the "Invalid Host header" error

❌ Paste the full error output (if available).

Invalid Host header

🖼️ Additional context (optional).

No response

Originally created by @adavi1995 on GitHub (Mar 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Habitica LXC ### 📂 What was the exact command used to execute the script? The one provided ### 📝 Provide a clear and concise description of the issue. Currently the command to install the script is broken - at least it was for me. This script is not finished for anyone who wants to reverse proxy it/external access or access with the app unless I am misunderstanding something, but after 2 days of struggling, and trying different things I have found that there are more steps to follow - cd /opt/habitica/website/client run the commands 'npm install' 'npm run build' - this one takes a hot minute. my config.json I changed the base_url to my subdomain e.g. https://habitica.domain.com here is the link where I have found the relevant commands https://github.com/HabitRPG/habitica/tree/develop/website/client I reverse proxied my ip with port 3000 (server port not the client) ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. To reproduce the issues I had, just install the script and try reverse proxying - I kept getting the "Invalid Host header" error ### ❌ Paste the full error output (if available). Invalid Host header ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:07:48 +03:00
OVERLORD commented 2026-02-04 20:07:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 4, 2025):

its not an script issue. The Script is an bare metal. You are welcome to write instructions in discussions on how to connect a reverse proxy, but we do not extend the script in this way.

@MickLesk commented on GitHub (Mar 4, 2025): its not an script issue. The Script is an bare metal. You are welcome to write instructions in discussions on how to connect a reverse proxy, but we do not extend the script in this way.
OVERLORD commented 2026-02-04 20:08:05 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

I can confirm that it's not even the reverse proxy that's doing this. I installed the script and am not able to connect going directly to the container on port 8080. I receive the same message Invalid Host header.

@chewbakartik commented on GitHub (Mar 10, 2025): I can confirm that it's not even the reverse proxy that's doing this. I installed the script and am not able to connect going directly to the container on port 8080. I receive the same message `Invalid Host header`.
OVERLORD commented 2026-02-04 20:08:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 10, 2025):

Look at discussions, there is an Guide. Dont write on old issuss

@MickLesk commented on GitHub (Mar 10, 2025): Look at discussions, there is an Guide. Dont write on old issuss
OVERLORD commented 2026-02-04 20:08:35 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

Hi @MickLesk, I want to start by thanking you for the hard work that you are putting into this project. I know it is greatly appreciated by more than just myself. I do however, have a couple of problems with the way that the conversation has gone on this particular issue.

The habitica scripts are a pretty new addition to the community scripts repository so it's natural for there to be some scenarios that come up where some people might need a little bit more help on. This particular "old" issue was raised 6 days ago and was summarily dismissed. My comment was trying to add some validation to what the initial poster raised. On a brand new instance of habitica, trying to navigate directly to the port 8080 I am experiencing the exact same issue as @adavi1995. This fact lends itself to seem like this issue was prematurely closed, and a further look into the problem is warranted.

My comment was to allow the community to know that this issue might not actually be related to the reverse proxy, and something else going on. I have looked at the other issue here on GitHub relating to Habitica (raised about the same time as this one) and found that the code snippet mentioned looks to be already in my brand new install.

Particularly in an open source project, GH Issues raised like this one aren't asking for an immediate fix by the maintainers, but providing a way for the community to discuss and attempt to help each other out. That's the type of stuff that makes open source fantastic. There are going to be many people who are utilizing the scripts in this project that might not necessarily have the technical background to dig deeper into issues. This project is a really great way for people to get their feet wet in that regards and expand their skill set.

As I get more time over the course of this week, I will dig into this issue deeper, and will respond to this ticket with my findings and potential fixes that could help @adavi1995, myself and any future person who searches up this exact same error message out.

Once again, I appreciate all of the hard work that you and all other contributers have been making on this project.

@chewbakartik commented on GitHub (Mar 10, 2025): Hi @MickLesk, I want to start by thanking you for the hard work that you are putting into this project. I know it is greatly appreciated by more than just myself. I do however, have a couple of problems with the way that the conversation has gone on this particular issue. The habitica scripts are a pretty new addition to the community scripts repository so it's natural for there to be some scenarios that come up where some people might need a little bit more help on. This particular "old" issue was raised 6 days ago and was summarily dismissed. My comment was trying to add some validation to what the initial poster raised. On a brand new instance of habitica, trying to navigate directly to the port 8080 I am experiencing the exact same issue as @adavi1995. This fact lends itself to seem like this issue was prematurely closed, and a further look into the problem is warranted. My comment was to allow the community to know that this issue might not actually be related to the reverse proxy, and something else going on. I have looked at the other issue here on GitHub relating to Habitica (raised about the same time as this one) and found that the code snippet mentioned looks to be already in my brand new install. Particularly in an open source project, GH Issues raised like this one aren't asking for an immediate fix by the maintainers, but providing a way for the community to discuss and attempt to help each other out. That's the type of stuff that makes open source fantastic. There are going to be many people who are utilizing the scripts in this project that might not necessarily have the technical background to dig deeper into issues. This project is a really great way for people to get their feet wet in that regards and expand their skill set. As I get more time over the course of this week, I will dig into this issue deeper, and will respond to this ticket with my findings and potential fixes that could help @adavi1995, myself and any future person who searches up this exact same error message out. Once again, I appreciate all of the hard work that you and all other contributers have been making on this project.
OVERLORD commented 2026-02-04 20:08:36 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 10, 2025):

If you read what @MickLesk said to you, you wouldn't have issues or need to "dig into this issue deeper". The solution is in the discussions, as Mick told you, here:

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

This a localy hosted instance of Habitica. If you want to expose it to the outside world, aka you have your own URL that you want to use to access the web page, you need few extra steps described in that discussion.

We always appreciate feedback on the scripts, but a minimum of effort is expected from the user before writing up issues on our github...

@tremor021 commented on GitHub (Mar 10, 2025): If you read what @MickLesk said to you, you wouldn't have issues or need to "dig into this issue deeper". The solution is in the discussions, as Mick told you, here: https://github.com/community-scripts/ProxmoxVE/discussions/2839 This a localy hosted instance of Habitica. If you want to expose it to the outside world, aka you have your own URL that you want to use to access the web page, you need few extra steps described in that discussion. We always appreciate feedback on the scripts, but a minimum of effort is expected from the user before writing up issues on our github...
OVERLORD commented 2026-02-04 20:08:44 +03:00
Author
Owner
Copy Link

@adavi1995 commented on GitHub (Mar 10, 2025):

@chewbakartik I misunderstood the script initially - it works as expected which is a bare metal setup, and can be tested via accessing locally. I posted the solution to what you are attempting in the discussion referenced by tremor021

@adavi1995 commented on GitHub (Mar 10, 2025): @chewbakartik I misunderstood the script initially - it works as expected which is a bare metal setup, and can be tested via accessing locally. I posted the solution to what you are attempting in the discussion referenced by tremor021
OVERLORD commented 2026-02-04 20:08:48 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 10, 2025):

Yes, thank you for that.

@tremor021 commented on GitHub (Mar 10, 2025): Yes, thank you for that.
OVERLORD commented 2026-02-04 20:08:50 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

If you read what I said in my comment, I was not discussing exposing it to the world. I did not set up a reverse proxy. I am stating that on a brand new instance of the system that I am getting the exact same error message as this ticket has.

Since I wrote my earlier comment, I have spun up a new instance and that one is working as expected. I am now going to be putting in the effort to try and determine why one worked and the other failed.

I'm going to compare both instances to see if I can figure out why 2 containers spun up the same way around 12 hrs apart on the same hypervisor are behaving so differently. I have a suspicion that it has to do with the LXC rebooting shortly after being provisioned. As it mentions on the script page, there's a delay before the web part is accessible, I think that there must be some npm tasks being run immediately after provisioning that the reboot disrupted.

@chewbakartik commented on GitHub (Mar 10, 2025): If you read what I said in my comment, I was not discussing exposing it to the world. I did not set up a reverse proxy. I am stating that on a brand new instance of the system that I am getting the exact same error message as this ticket has. Since I wrote my earlier comment, I have spun up a new instance and that one is working as expected. I am now going to be putting in the effort to try and determine why one worked and the other failed. I'm going to compare both instances to see if I can figure out why 2 containers spun up the same way around 12 hrs apart on the same hypervisor are behaving so differently. I have a suspicion that it has to do with the LXC rebooting shortly after being provisioned. As it mentions on the script page, there's a delay before the web part is accessible, I think that there must be some npm tasks being run immediately after provisioning that the reboot disrupted.
OVERLORD commented 2026-02-04 20:08:56 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

If you read what @MickLesk said to you, you wouldn't have issues or need to "dig into this issue deeper". The solution is in the discussions, as Mick told you, here:

#2839

This a localy hosted instance of Habitica. If you want to expose it to the outside world, aka you have your own URL that you want to use to access the web page, you need few extra steps described in that discussion.

We always appreciate feedback on the scripts, but a minimum of effort is expected from the user before writing up issues on our github...

Thank you for sharing the link to the reverse proxy guide and thanks to @adavi1995 for writing it up.

@chewbakartik commented on GitHub (Mar 10, 2025): > If you read what [@MickLesk](https://github.com/MickLesk) said to you, you wouldn't have issues or need to "dig into this issue deeper". The solution is in the discussions, as Mick told you, here: > > [#2839](https://github.com/community-scripts/ProxmoxVE/discussions/2839) > > This a localy hosted instance of Habitica. If you want to expose it to the outside world, aka you have your own URL that you want to use to access the web page, you need few extra steps described in that discussion. > > We always appreciate feedback on the scripts, but a minimum of effort is expected from the user before writing up issues on our github... Thank you for sharing the link to the reverse proxy guide and thanks to @adavi1995 for writing it up.
OVERLORD commented 2026-02-04 20:09:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 10, 2025):

I only pointed this out because we often don't notice it because these issues are filtered out. I didn't have a push for it either, I just happened to see it when it was updated, so my advice was to open a new one or start a discussion in the discussion area. / or to read the guide ^^

@MickLesk commented on GitHub (Mar 10, 2025): I only pointed this out because we often don't notice it because these issues are filtered out. I didn't have a push for it either, I just happened to see it when it was updated, so my advice was to open a new one or start a discussion in the discussion area. / or to read the guide ^^
OVERLORD commented 2026-02-04 20:09:24 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

OK, last post on this thread in the hopes that it helps future people.

The initial state of this script allows for habitica to ONLY be accessed via IP address. If you have your home DNS register new hosts to be accessible by your internal domain and the host name, it will NOT work.

Second, you do need to wait some time after the container starts in order for npm to do its thing before rebooting or you will have it be in an inconsistent state. If you can access Habitica @ http://IP_ADDRESS:8080 then you're good to go.

If for whatever reason your container rebooted too quickly, follow the instructions in @adavi1995's guide (https://github.com/community-scripts/ProxmoxVE/discussions/2839) for rebuilding the client.

@MickLesk it's all good, I understand for your perspective for new issues to be raised in order for visibility. I was approaching this from the perspective of a person who found the same error message in the project as what I was experiencing, and having it closed with no helpful resolution. I always try to follow up in that event, since it's not likely that I'll be the only one who comes across it again in the future.

@chewbakartik commented on GitHub (Mar 10, 2025): OK, last post on this thread in the hopes that it helps future people. The initial state of this script allows for habitica to ONLY be accessed via IP address. If you have your home DNS register new hosts to be accessible by your internal domain and the host name, it will NOT work. Second, you do need to wait some time after the container starts in order for npm to do its thing before rebooting or you will have it be in an inconsistent state. If you can access Habitica @ http://IP_ADDRESS:8080 then you're good to go. If for whatever reason your container rebooted too quickly, follow the instructions in @adavi1995's guide (https://github.com/community-scripts/ProxmoxVE/discussions/2839) for rebuilding the client. @MickLesk it's all good, I understand for your perspective for new issues to be raised in order for visibility. I was approaching this from the perspective of a person who found the same error message in the project as what I was experiencing, and having it closed with no helpful resolution. I always try to follow up in that event, since it's not likely that I'll be the only one who comes across it again in the future.
OVERLORD commented 2026-02-04 20:09:33 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 10, 2025):

We literaly have this on script page. Not sure why would you reboot or something:

Image

@tremor021 commented on GitHub (Mar 10, 2025): We literaly have this on script page. Not sure why would you reboot or something: ![Image](https://github.com/user-attachments/assets/2a0e7745-8894-4631-a7a8-1311b4c6370e)
OVERLORD commented 2026-02-04 20:09:38 +03:00
Author
Owner
Copy Link

@chewbakartik commented on GitHub (Mar 10, 2025):

We literaly have this on script page. Not sure why would you reboot or something:

Image

Sometimes things happen outside of our control.

@chewbakartik commented on GitHub (Mar 10, 2025): > We literaly have this on script page. Not sure why would you reboot or something: > > ![Image](https://github.com/user-attachments/assets/2a0e7745-8894-4631-a7a8-1311b4c6370e) Sometimes things happen outside of our control.
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#584
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?