Installing TrueNAS SCALE on a VPS using a Custom ISO

[HeyYuvraj]

What topic does your proposed suggestion relate to?

Virtual Private Servers (VPS), custom ISO installation, storage & NAS solutions, Linux system administration

How do you aim to structure your proposed change?

Introduction

• Brief overview of TrueNAS SCALE
• Use cases for running TrueNAS SCALE on a VPS
• Important limitations and considerations

Prerequisites

• Minimum system requirements
• Required access (VNC, ISO upload permissions)

Booting the ISO

• Navigating the ZAP control panel
• choosing custom ISO
• Setting the ISO as boot media

Installing TrueNAS SCALE

• Booting via VNC
• Installation steps
• Disk selection and warnings
• Completing installation and rebooting

Initial Configuration

• Web UI access
• Network configuration
• Default credentials and security steps

Troubleshooting

• Boot issues
• Network access problems
• Common installation errors

Conclusion

• Summary
• Recommended use cases

Could you briefly summarise the contents you plan to write about to ensure you have the appropriate technical knowledge?

• Explanation of what TrueNAS SCALE is and when to use it
• Step-by-step guide to installing TrueNAS SCALE
• Accessing and securing the TrueNAS web interface
• Common issues users may face and how to resolve them

What is your ZAP ID?

zap480562

What is your Discord ID?

646310108116287518

Do you have any previous experience in writing and publishing articles?

I have experience writing technical guides and step-by-step documentation, I previously wrote: https://zap-hosting.com/guides/docs/dedicated-windows-fs-22-epic . I focus on clear instructions, practical examples, and troubleshooting tips to help users of all skill levels.

Additional Information

The article will help users understand both the possibilities and limitations of running TrueNAS on a VPS.

Do you depend on a service for creating your guide?

Yes. I would require temporary access to a VPS.

By submitting this form, you agree that...

• You have read and understood our contribution section on our documentation.
• You understand our guidelines and conditions that exist.
• Your suggestion is original and not a duplicate.
• You have provided the correct ZAP ID.
• You have answered this suggestion form to the best of your ability.
• You agree to receive feedback and communicate with our ZAP docs team.
• You agree to the ZAP-Hosting Contribution Program Terms & Conditions, which can be accessed here.

[fgalz]

Hi @HeyYuvraj,

TrueNAS SCALE is fundamentally designed as a bare metal storage solution. Direct access to physical data carriers is required for meaningful use. In virtualized environments with abstracted block devices, limitations in disks, this prerequisite is barely met, meaning that TrueNAS SCALE can only be used to a very limited extent and without clear added value.

The TrueNAS SCALE ISO was not really provided as a recommended production solution, but because individual customers requested this ISO for learning, testing or experimental purposes.

It can be operated for such scenarios, but it is rather suitable for meaningful productive use as a NAS or storage solution on our VPS products. Before we decide whether a guide is useful at all, it would be important to know what specific information you would like to implement in there.

[HeyYuvraj]

Hi @fgalz ,

Thanks for the clarification and I agree with your assessment.

My original idea was based on working with the TrueNAS SCALE ISO strictly for testing and learning purposes. During that process, I noticed that installing the ISO requires some platform-specific steps like initial network access that are currently not documented, meaning users have to find these steps on their own.

That said, I understand that TrueNAS SCALE on VPS offers very limited value. If it is more appropriate, I’m happy to scope the guide primarily to Dedicated Servers, where SCALE is actually designed to be used and either omit VPS usage entirely or mention it only as experimental/testing, with clear limitations.

The intention is documentation completeness and reducing trial-and-error, not promoting unsupported use cases.

Please let me know what scope you consider appropriate.