SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

File path mismatches in Crafty Controller updater #2013

New Issue
Closed
opened 2025-11-20 05:21:49 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:21:49 -05:00
Owner
Copy Link

Originally created by @dqni710 on GitHub (Oct 5, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Crafty Controller

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📈 Which Proxmox version are you on?

pve-manager/9.0.3/025864202ebb6109

📝 Provide a clear and concise description of the issue.

The update script uses /opt/crafty-controller as Crafty's installation path, but in reality it is /var/opt/minecraft with Crafty 4 and onwards. This causes the update script to never function properly.

🔄 Steps to reproduce the issue.

Step 1: Run the script in a healthy Crafty Controller installation
Step 2: Observe

❌ Paste the full error output (if available).

✖️ No Crafty-Controller Installation Found!

🖼️ Additional context (optional).

No response

Originally created by @dqni710 on GitHub (Oct 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Crafty Controller ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/crafty-controller.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📈 Which Proxmox version are you on? pve-manager/9.0.3/025864202ebb6109 ### 📝 Provide a clear and concise description of the issue. The update script uses `/opt/crafty-controller` as Crafty's installation path, but in reality it is `/var/opt/minecraft` with Crafty 4 and onwards. This causes the update script to never function properly. ### 🔄 Steps to reproduce the issue. Step 1: Run the script in a healthy Crafty Controller installation Step 2: Observe ### ❌ Paste the full error output (if available). ✖️ No Crafty-Controller Installation Found! ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:21:49 -05:00
saavagebueno commented 2025-11-20 05:21:49 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 6, 2025):

@CrazyWolf13

@michelroegl-brunner commented on GitHub (Oct 6, 2025): @CrazyWolf13
saavagebueno commented 2025-11-20 05:21:49 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 6, 2025):

@cz-cs The installation path is not in/var/opt/crafty.

The script is configured to use /opt/crafty

I just confirmed this on my own instance running since I created this script initially and uploaded it to this repo.

Can you run the following?

ls -al /var/opt/crafty
ls -al /opt/crafty
ls -al /opt/crafty/crafty-4
@CrazyWolf13 commented on GitHub (Oct 6, 2025): @cz-cs The installation path is not in/var/opt/crafty. The script is configured to use /opt/crafty I just confirmed this on my own instance running since I created this script initially and uploaded it to this repo. Can you run the following? ```bash ls -al /var/opt/crafty ls -al /opt/crafty ls -al /opt/crafty/crafty-4 ```
saavagebueno commented 2025-11-20 05:21:50 -05:00
Author
Owner
Copy Link

@dqni710 commented on GitHub (Oct 6, 2025):

Output:
ls: cannot access '/var/opt/crafty': No such file or directory
ls: cannot access '/opt/crafty': No such file or directory
ls: cannot access '/opt/crafty/crafty-4': No such file or directory

I think I updated Crafty myself, and the installer placed it in /var/opt/minecraft/crafty...
The script should be updated to accommodate the installer's default path, though. If there's a flag that can be set for /opt/crafty or something along those lines then that would be better. /var/opt is an unusual place to install

@dqni710 commented on GitHub (Oct 6, 2025): Output: `ls: cannot access '/var/opt/crafty': No such file or directory` `ls: cannot access '/opt/crafty': No such file or directory` `ls: cannot access '/opt/crafty/crafty-4': No such file or directory` I think I updated Crafty myself, and the installer placed it in `/var/opt/minecraft/crafty`... The script should be updated to accommodate the installer's default path, though. If there's a flag that can be set for `/opt/crafty` or something along those lines then that would be better. `/var/opt` is an unusual place to install
saavagebueno commented 2025-11-20 05:21:50 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 7, 2025):

@cz-cs Yeah that sounds like the problem to me, unfortunately that's a bit difficult now as this probably messed up all your paths.

We have a standard policy to place as much apps as possible under /opt/{appname} and as this works perfectly fine for crafty this is what we did here.

@CrazyWolf13 commented on GitHub (Oct 7, 2025): @cz-cs Yeah that sounds like the problem to me, unfortunately that's a bit difficult now as this probably messed up all your paths. We have a standard policy to place as much apps as possible under /opt/{appname} and as this works perfectly fine for crafty this is what we did here.
saavagebueno commented 2025-11-20 05:21:50 -05:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 7, 2025):

As this fully removed your /opt/crafty path there isn't much we can do, maybe you have a backup before you messed with the installer, otherwise I suggest exporting the worlds and doing a fresh install.

As you messed around with the crafty installer to update the app, we can't really support this.

@CrazyWolf13 commented on GitHub (Oct 7, 2025): As this fully removed your /opt/crafty path there isn't much we can do, maybe you have a backup before you messed with the installer, otherwise I suggest exporting the worlds and doing a fresh install. As you messed around with the crafty installer to update the app, we can't really support this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2013
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?