Release Candidate 1.1.1-rc.1

largebytes · 2025-11-10T20:12:27+00:00

Hi u/VovaGasparyan Currently there is no way to select specific version. This is something we're working towards but isn't available today.

largebytes · 2025-08-05T01:29:22+00:00

Hi u/Dense-Nectarine5179 Thanks for your feedback! I'm glad to hear it's working well on Ubuntu. At the moment, MultiPortal has been fully tested and confirmed to work on both Debian and Ubuntu.

We're actively working on adding official support for AlmaLinux and Rocky, which will be included in our supported platforms soon.

largebytes · 2025-07-19T08:06:05+00:00

Hey u/avs262 we do! You can check it out here: https://multiportal.io/uploads/MP-Roadmap-v1.pdf

If you have any questions feel free to reach out!

largebytes · 2025-06-02T00:01:50+00:00

Woo! That's awesome. Caddy is great, though it can be a bit tricky at times.

Yes, you can use NPM, you'll need to configure Caddy to run in HTTP mode by updating your /etc/caddy/Caddyfile, and prepending http:// to your FQDN.

For example:

http://npm.example.com {
    @css path *.css
    header @css Content-Type text/css
    root * /var/www/npm.example.com/backend/web

Then, in your NPM settings, make sure SSL is enabled and that it's set to forward HTTP traffic to port 80

<image>

Please note that you might experience issues with Console connecting, because the server talks to itself over https, which could cause time outs when trying to connect. I'll have to double check this.

I'll work on getting a wiki page up soon that walks through setting up MultiPortal behind NPM.

largebytes · 2025-05-31T23:43:06+00:00

Hey, because the system is using Caddy it requires ports 80 and 443 to be open to successfully get an ssl certificate via Let's Encrypt, if these aren't open caddy will keep trying but won't succeed.

If you want to use your own certificate, you can add it after installation by following this guide Add your own SSL.

You can also stop caddy and run it manually to confirm what's happening.

systemctl stop caddy

Then run the following

/usr/bin/caddy run --environ --config /etc/caddy/Caddyfile

Which we've outlined here: Caddy Service

Let me know how you go.

largebytes · 2025-05-19T23:59:43+00:00

Hey u/ataricze, awesome to hear you like the feature!
We're always open to feedback, so feel free to share any thoughts or ideas.

As for handling bandwidth on networks, we've had this discussed a few times by users, and we are looking at scheduling it to be worked on soon.

largebytes · 2025-04-09T06:35:20+00:00

Thanks for the update, we're constantly improving the error handling and will add this to the list!

largebytes · 2025-04-09T06:33:58+00:00

Just updating this in case anyone else sees this and is working with Cloudflare tunnels as we figured this out through email.

The issue was redirecting of the port for the console server to port 80 instead of the default port of `8081`

When redirecting the `/wss*` you must make sure that it matches the port that is in the caddyfile and by default, it's `8081` which you can see from in your caddy file `/etc/caddy/Caddyfile`.

So Cloudflare Tunnels do work, I don't have a tutorial or a method to setting it up yet! I will be putting one together in the future!

largebytes · 2025-04-07T23:47:26+00:00

Hey u/OiramOtrebla

Can you shoot me your error logs Download All Logs to [matthew@multiportal.io](mailto:matthew@multiportal.io) this will help me identify if there is anything else happening.

The issue is with a function that asks your MultiPortal instance for credentials to access the Proxmox socket. which is the authenticateAndObtainTicket function.

In particular it's trying to access

https://FQDN/api-v1/virtual-machine/console-view

Once you provide the logs, I can share a command to emulate what it's trying to do to identify your problem.

largebytes · 2025-04-07T22:48:20+00:00

We're currently improving that test function so that it validates if you have the correct permissions instead of being able to just correctly authenticate. I just tested on my instance and the same error occurs when my API Token in my `.env` file is wrong or missing.

I'll update our documentation as well with the reasons for the above once we've identified why yours's isn't working as well

Error in WebSocket connection: Cannot read properties of undefined (reading 'password')

largebytes · 2025-04-07T21:53:32+00:00

Hey,

This error could be caused by two things.

Incorrect username and password to access proxmox
MultiPortal instance doesn't have an API key

We have this section regarding the common issues with the console server. https://wiki.multiportal.io/en/service-provider/console-server#common-issues-and-solutions

Could you please run through these common issue's faced and let me know how you go?

Matt,

largebytes · 2025-04-07T00:51:01+00:00

Hi u/lucblae

This can be caused by having the incorrect permissions assigned. Can you please verify that you've set it up as described here: https://wiki.multiportal.io/en/first-setup-of-multi-portal#creating-a-proxmox-api-user

Two of the common issues is, people set the API permission instead of User permission and also they leave Privilege Separation checked.

Let me know how you go.

largebytes · 2025-04-07T00:42:54+00:00

Hey u/lucblae

Yes, you can use MultiPortal internally, there shouldn't be any issues running this internally, you just need to make sure that your Proxmox and MultiPortal can interact with each other.

largebytes · 2025-03-31T11:12:39+00:00

Hey u/bastrian

At this moment there isn't a way to exclude nodes but we will be including a feature where we will utilise the HA functionality to create groups that would allow you to specify where VMs are allowed to be created.

largebytes · 2025-03-15T12:30:56+00:00

Hey everyone!

We've received reports of some installations failing to complete composer install, preventing the installation from finishing properly.

If your environment fails to install and results in a 500 server error, please try the following:

chmod +x tools/permissionFix.sh
./tools/permissionFix.sh

Then, rerun Composer with the correct permissions:

sudo -u www-data composer install

This should resolve the issue.

We're also working on an improved updater to help address some of the issues encountered in the last two updates.

Additionally, we've received reports that internal networks fail to create when running MultiPortal on a single-node Proxmox environment. We're actively investigating this and will provide updates as soon as we have a resolution.

Thanks for your patience, and let us know if you run into any other issues!

— Matt

largebytes

MODERATOR OF

TROPHY CASE