# 🚀 YunoHost 12.0 (Bookworm) release / Sortie de YunoHost 12.0 (Bookworm)

**URL:** https://forum.yunohost.org/t/yunohost-12-0-bookworm-release-sortie-de-yunohost-12-0-bookworm/31673
**Category:** Announcements
**Tags:** ynh\_release, french, english
**Created:** [October 31, 2024, 12:37pm UTC](https://forum.yunohost.org/t/yunohost-12-0-bookworm-release-sortie-de-yunohost-12-0-bookworm/31673 "2024-10-31T12:37:00Z")
**Posts on this page:** 1
**Showing post:** 82

<div class="post-metadata">

### Author: ![tmb](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/t/7c8e57/32.png) [@tmb](https://forum.yunohost.org/u/tmb)
#### Post date: [November 4, 2024, 12:27pm UTC](https://forum.yunohost.org/t/yunohost-12-0-bookworm-release-sortie-de-yunohost-12-0-bookworm/31673/82 "2024-11-04T12:27:36Z")

</div>

> [@AxlRose1976](#):
>
> it´s sad that I can´t move the portal to the domain that I´d like to. It was possible with yunohost 11 when I set a subdomain as main domain and the portal showed up on this domain.

Hm, can someone maybe provide a little bit more explanation, about changes in the intented use (if any), and the available settings that remain with the new YNH 12 portal implementation? (I’m sorry, I also could not yet fully ‘grasp’ or ‘grok’ this part from the announcement.)

Here is another related use-case with (to me) unknown support state that worked really nice with YNH 11:

- Main domain set to a possibly hard-to-remember, maybe even impossible to change, reverse-DNS Domain. (Used as smtp mail-out domain by all configured domains)
- While allowing users to log in on a subdomain of their “usual” domain. (It’s much simpler to explain own users to just use e.g. to `https://apps.example.org` if they want or need to sign in to something. While `example.org` and `www.example.org` can just redirect/host some (public) app or website.

In YNH 11 the domain allowing the login could be configured by having a file `/etc/ssowat/conf.json.persistent` with:

```auto
{ "portal_domain": "apps.example.org" }

```

**Result:** Except for the button “user interface” (only present?) in the admin’s web interface, everything seems to point to the correct portal domain, and work perfectly.

1. Is this expected to break when upgrading to YNH 12?

2. Do you see an alternative solution that does **not require** the users to use **long yunohost login url/sub-paths**?

* * *

PS: As reference, that “portal\_domain” configuration option had come up e.g. in this thread:

> [@Users can't login after changing default page from domain.tld to sub.domain.tld](https://forum.yunohost.org/t/users-cant-login-after-changing-default-page-from-domain-tld-to-sub-domain-tld/23342/8):
>
> I think. In the domain menu, I clicked on make default, I thought it just changed the yunohost access domain. (to the sso page, admin page etc) I have 3 domain link to that install domain0.tld, domain1.tld and domain3.tld right now, I access to yunohost via domain0.tld, but I want to use it for other purpose, so I made default sub.domain0.tld "portal\_domain": "sub.domain0.tld", "portal\_path": "/yunohost/sso/", "redirected\_regex": { "sub.domain0.tld/yunohost[\\/]?$": "htt…

---

_[View the full topic](https://forum.yunohost.org/t/yunohost-12-0-bookworm-release-sortie-de-yunohost-12-0-bookworm/31673)._