Are you in a special context or did you perform specific tweaking on your YunoHost instance ?
No
Describe your issue
I cannot access the FreshRSS web address via the app interface. FreshRSS is the only app I have, and I have never accessed its interface through the local apps since the server installation. I received an access privilege error, so I granted all privileges it, but later I checked the failed systemctl processes.
My user requires configuration, which prevents me from enabling the user@ process. I believe I cannot access it because ***.local is down. I need to resolve that issue first. Any help would be greatly appreciated.
$ sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
⚫ user@46804.service loaded failed failed User Manager for UID 46804
$ id -u
46804
$ sudo systemctl enable user@46804
The unit files have no installation config (WantedBy=, RequiredBy=, Also, Alias settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.
A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.
A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).
In case of template units, the unit is meant to be enabled with some instance name specified.
I edited my question with AI and some meanings are lose its details. Let me clarify things moreover and bear with me some possible unrelated details.
Installation
I installed VM iso and thne used curl https://install.yunohost.org | bash
this for yunohost installation. whenever finished installation I tries to install freshrss immediatelly for test. I didn’t do any additional real domain just used local domin for basic requirements.
Accessing server apps error
I just want to test freshrss that’s why I installed yunohost. I couldn’t access installed freshrss app’s interface when I tried to open it with following error. This site can’t be reached ***.local’s DNS address could not be found. Diagnosing the problem. DNS_PROBE_POSSIBLE error like this for no access after long loading time.
I wouldn’t access it and I thought “maybe there is privilege error”
To solve possible privilege error, I opened privileges of freshrss from https://192.168.1.167/yunohost/admin/#/apps/freshrss/operations
gave un given priviledges to admin FreshRSS, FreshRSS (api), E-mail, XMPP from Admins section from https://192.168.1.167/yunohost/admin/#/groups. but it isn’t worked. I didn’t get any proced for open freshrss page got access problem just previous. I searched for error and found clue about just above error no different one.
Thigs seems I’ve more crucial error
So I skipped the privilege section cause thought that it doesn’t related freshrss or apps things cause I’ve server’s page access error. Just have access yunohost interface and nothing more.
More deeper outlook
I shared above errors for more intuitive approach to the reason why I’ve possible have this error.
`
It is the command took with the sudo priviledges of user of the same yunohost admin on the VM screen and yunohost interface additionally not with ssh.
I was restarted the VM and then got one more error. Possibly occurred by successfull attempt to log in with another user this time.
$ sudo systemctl --failed
LOAD ACTIVE SUB
UNIT DESCRIPTION
● user@1000.service loaded failed failed User Manager for UID 1000
● user@46804.service loaded failed failed User Manager for UID 46804
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state; values depend on unit type.
This is Failed: 2 units. processes of systemctl details
Requested user errors
$ sudo journalctl -efu user@1000
Oct 21 00:22:47 yunohost systemd[1]: Started User Manager for UID 1000. Boot 2de19d101e2d4e0d8725717a977d1447
Oct 21 00:26:27 yunohost systemd[1]: Starting User Manager for UID 1000...
Oct 21 00:26:27 yunohost systemd[446]: pam_unix(systemd-user:session): session opened for user openwrt (uid=1000) by (uid=0)
Oct 21 00:26:27 yunohost systemd[446]: Queued start job for default target Main User Target.
Oct 21 00:26:27 yunohost systemd[446]: Reached target Paths.
Oct 21 00:26:27 yunohost systemd[446]: Reached target Sockets.
Oct 21 00:26:27 yunohost systemd[446]: Reached target Timers.
Oct 21 00:26:27 yunohost systemd[446]: Reached target Basic System.
Oct 21 00:26:27 yunohost systemd[446]: Reached target Main User Target.
Oct 21 00:26:27 yunohost systemd[446]: Startup finished in 36ms.
Oct 21 00:26:27 yunohost systemd[1]: Started User Manager for UID 1000. Boot 99f52b473cc948698911f5f989da3225
Oct 21 01:08:20 yunohost systemd[1]: Starting User Manager for UID 1000...
Oct 21 01:08:20 yunohost systemd[454]: pam_unix(systemd-user:session): session opened for user openwrt (uid=1000) by (uid=0)
Oct 21 01:08:20 yunohost systemd[454]: Queued start job for default target Main User Target.
Oct 21 01:08:20 yunohost systemd[454]: Reached target Paths.
Oct 21 01:08:20 yunohost systemd[454]: Reached target Sockets.
Oct 21 01:08:20 yunohost systemd[454]: Reached target Timers.
Oct 21 01:08:20 yunohost systemd[454]: Reached target Basic System.
Oct 21 01:08:20 yunohost systemd[454]: Reached target Main User Target.
Oct 21 01:08:20 yunohost systemd[454]: Startup finished in 37ms.
Oct 21 01:08:20 yunohost systemd[1]: Started User Manager for UID 1000. Boot 857e3709c61b4224aab9d5b00ccd0d3e
Oct 24 00:11:16 ***.local systemd[1]: Starting User Manager for UID 1000...
Oct 24 00:11:16 ***.local systemd[1385]: pam_unix(systemd-user:session): session opened for user openwrt (uid=1000) by (uid=0)
Oct 24 00:11:16 ***.local systemd[1385]: Failed to determine supported controllers: No such process
Oct 24 00:11:16 ***.local systemd[1385]: Failed to allocate manager object: No such process
Oct 24 00:11:16 ***.local systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
Oct 24 00:11:16 ***.local systemd[1]: user@1000.service: Failed with result 'exit-code'.
Oct 24 00:11:16 ***.local systemd[1]: Failed to start User Manager for UID 1000.
~$ sudo journalctl -efu user@46804
Journal begins at Sun 2024-10-20 23:49:14 EEST.
Oct 22 14:18:48 ***.local systemd[1]: Starting User Manager for UID 46804...
Oct 22 14:18:48 ***.local systemd[1543]: pam_unix(systemd-user:session): session opened for user xemilian (uid=46804) by (uid=0)
Oct 22 14:18:48 ***.local systemd[1543]: Failed to determine supported controllers: No such process
Oct 22 14:18:48 ***.local systemd[1543]: Failed to allocate manager object: No such process
Oct 22 14:18:48 ***.local systemd[1]: user@46804.service: Main process exited, code=exited, status=1/FAILURE
Oct 22 14:18:48 ***.local systemd[1]: user@46804.service: Failed with result 'exit-code'.
Oct 22 14:18:48 ***.local systemd[1]: Failed to start User Manager for UID 46804.
Boot c3cb083e2f934d9ca6228120353bb82e
Oct 23 11:45:30 ***.local systemd[1]: Starting User Manager for UID 46804...
Oct 23 11:45:30 ***.local systemd[1908]: pam_unix(systemd-user:session): session opened for user xemilian (uid=46804) by (uid=0)
Oct 23 11:45:30 ***.local systemd[1908]: Failed to determine supported controllers: No such process
Oct 23 11:45:30 ***.local systemd[1908]: Failed to allocate manager object: No such process
Oct 23 11:45:30 ***.local systemd[1]: user@46804.service: Main process exited, code=exited, status=1/FAILURE
Oct 23 11:45:30 ***.local systemd[1]: user@46804.service: Failed with result 'exit-code'.
Oct 23 11:45:30 ***.local systemd[1]: Failed to start User Manager for UID 46804.
Boot 857e3709c61b4224aab9d5b00ccd0d3e
Oct 24 00:57:33 ***.local systemd[1]: Starting User Manager for UID 46804...
Oct 24 00:57:33 ***.local systemd[1618]: pam_unix(systemd-user:session): session opened for user xemilian (uid=46804) by (uid=0)
Oct 24 00:57:33 ***.local systemd[1618]: Failed to determine supported controllers: No such process
Oct 24 00:57:33 ***.local systemd[1618]: Failed to allocate manager object: No such process
Oct 24 00:57:33 ***.local systemd[1]: user@46804.service: Main process exited, code=exited, status=1/FAILURE
Oct 24 00:57:33 ***.local systemd[1]: user@46804.service: Failed with result 'exit-code'.
Oct 24 00:57:33 ***.local systemd[1]: Failed to start User Manager for UID 46804.
$ sudo journalctl -xe
...
Oct 24 00:57:33 ***.local systemd[1]: Created slice User Slice of UID 46804.
Subject: A start job for unit user-46804.slice has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit user-46804.slice has finished successfully.
The job identifier is 730.
Oct 24 00:57:33 ***.local systemd[1]: Starting User Runtime Directory /run/user/46804.
Subject: A start job for unit user-runtime-dir@46804.service has begun execution
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit user-runtime-dir@46804.service has begun execution.
The job identifier is 729.
Oct 24 00:57:33 ***.local systemd-logind[385]: New session 9 of user xemilian.
Subject: A new session 9 has been created for user xemilian
Defined-By: systemd
Support: https://www.debian.org/support
Documentation: sd-login(3)
A new session with the ID 9 has been created for the user xemilian.
The leading process of the session is 1606.
Oct 24 00:57:33 ***.local systemd[1]: Finished User Runtime Directory /run/user/46804.
Subject: A start job for unit user-runtime-dir@46804.service has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit user-runtime-dir@46804.service has finished successfully.
The job identifier is 729.
Oct 24 00:57:33 ***.local systemd[1]: Starting User Manager for UID 46804.
Subject: A start job for unit user@46804.service has begun execution
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit user@46804.service has begun execution.
The job identifier is 728.
Oct 24 00:57:33 ***.local systemd[1618]: pam_unix(systemd-user:session): session opened for user xemilian (uid=46804) by (uid=0)
Oct 24 00:57:33 ***.local systemd[1618]: Failed to determine supported controllers: No such process
Oct 24 00:57:33 ***.local systemd[1618]: Failed to allocate manager object: No such process
Oct 24 00:57:33 ***.local systemd[1]: user@46804.service: Main process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: https://www.debian.org/support
An ExecStart= process belonging to unit user@46804.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Oct 24 00:57:33 ***.local systemd[1]: user@46804.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://www.debian.org/support
The unit user@46804.service has entered the 'failed' state with result 'exit-code'.
Oct 24 00:57:33 ***.local systemd[1]: Failed to start User Manager for UID 46804.
Subject: A start job for unit user@46804.service has failed
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit user@46804.service has finished with a failure.
The job identifier is 728 and the job result is failed.
Oct 24 00:57:33 ***.local systemd[1]: Started Session 9 of user xemilian.
Subject: A start job for unit session-9.scope has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support
...
reports:
0:
description: Base system
id: basesystem
items:
0:
details: Server model is innotek GmbH VirtualBox
status: INFO
summary: Server hardware architecture is oracle amd64
1:
status: INFO
summary: Server is running Linux kernel 5.10.0-33-amd64
2:
status: INFO
summary: Server is running Debian 11.11
3:
details:
- yunohost version: 11.2.31 (stable)
- yunohost-admin version: 11.2.8 (stable)
- moulinette version: 11.2.1 (stable)
- ssowat version: 11.2.1.1 (stable)
status: INFO
summary: Server is running YunoHost 11.2.31 (stable)
1:
description: Internet connectivity
id: ip
items:
0:
status: SUCCESS
summary: Domain name resolution is working!
1:
details:
- Global IP: ***.***.***.***
- Local IP: 192.168.1.167
status: SUCCESS
summary: The server is connected to the Internet through IPv4!
2:
details: |
IPv6 should usually be automatically configured by the system or your provider if it's available.
Otherwise, you might need to configure a few things manually as explained in the documentation here:
https://yunohost.org/ipv6.
status: WARNING
summary: The server does not have working IPv6.
2:
description: DNS records
id: dnsrecords
items:
status: INFO
summary: Domain ***.local is based on a special-use top-level domain (TLD) such as .local or .test and is therefore not expected to have actual DNS records.
3:
description: Ports exposure
id: ports
items:
0:
details:
- Exposing this port is needed for admin features (service ssh)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 22 is not reachable from the outside.
1:
details:
- Exposing this port is needed for email features (service postfix)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 25 is not reachable from the outside.
2:
details:
- Exposing this port is needed for web features (service nginx)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 80 is not reachable from the outside.
3:
details:
- Exposing this port is needed for web features (service nginx)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 443 is not reachable from the outside.
4:
details:
- Exposing this port is needed for email features (service postfix)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 587 is not reachable from the outside.
5:
details:
- Exposing this port is needed for IMAP features (service dovecot)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 993 is not reachable from the outside.
6:
details:
- Exposing this port is needed for XMPP features (service metronome)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 5222 is not reachable from the outside.
7:
details:
- Exposing this port is needed for XMPP features (service metronome)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
status: ERROR
summary: Port 5269 is not reachable from the outside.
4:
description: Web
id: web
items:
status: INFO
summary: Domain *hostname*.local is based on a special-use top-level domain (TLD) such as .local or .test and is therefore not expected to be exposed outside the local network.
5:
description: Email
id: mail
items:
0:
details:
- You should first try to unblock outgoing port 25 in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
- Some providers won't let you unblock outgoing port 25 because they don't care about Net Neutrality.
- Some of them provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass these kinds of limits. See https://yunohost.org/vpn_advantage
- You can also consider switching to a more net neutrality-friendly provider.
status: ERROR
summary: The SMTP mail server cannot send emails to other servers because outgoing port 25 is blocked in IPv4.
1:
details: |
Could not open a connection on port 25 to your server in IPv4. It appears to be unreachable.
1. The most common cause for this issue is that port 25 is not correctly forwarded to your server.
2. You should also make sure that service postfix is running.
3. On more complex setups: make sure that no firewall or reverse-proxy is interfering.
status: ERROR
summary: The SMTP mail server is unreachable from the outside on IPv4. It won't be able to receive emails.
2:
details:
- You should first try to configure reverse DNS with *hostname*.local in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
- Some providers won't let you configure your reverse DNS (or their feature might be broken). If you are experiencing issues because of this, consider the following solutions:
- Some ISPs provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://yunohost.org/vpn_advantage
- Or it's possible to switch to a different provider.
status: ERROR
summary: No reverse DNS is defined in IPv4. Some emails may fail to get delivered or be flagged as spam.
3:
status: SUCCESS
summary: The IPs and domains used by this server do not appear to be blacklisted.
4:
status: SUCCESS
summary: 0 pending emails in the mail queues.
6:
description: Services status check
id: services
items:
0:
status: SUCCESS
summary: Service dnsmasq is running!
1:
status: SUCCESS
summary: Service dovecot is running!
2:
status: SUCCESS
summary: Service fail2ban is running!
3:
status: SUCCESS
summary: Service metronome is running!
4:
status: SUCCESS
summary: Service mysql is running!
5:
status: SUCCESS
summary: Service nginx is running!
6:
status: SUCCESS
summary: Service php7.4-fpm is running!
7:
status: SUCCESS
summary: Service php8.2-fpm is running!
8:
status: SUCCESS
summary: Service postfix is running!
9:
status: SUCCESS
summary: Service redis-server is running!
10:
status: SUCCESS
summary: Service rspamd is running!
11:
status: SUCCESS
summary: Service slapd is running!
12:
status: SUCCESS
summary: Service ssh is running!
13:
status: SUCCESS
summary: Service yunohost-api is running!
14:
status: SUCCESS
summary: Service yunohost-firewall is running!
15:
status: SUCCESS
summary: Service yunomdns is running!
7:
description: System resources
id: systemresources
items:
0:
status: SUCCESS
summary: The system still has 6.9 GiB (91%) RAM available out of 7.6 GiB.
1:
details: Please be careful and aware that if the server is hosting swap on an SD card or SSD storage, it may drastically reduce the life expectancy of the device.
status: SUCCESS
2:
status: ERROR
summary: Storage / (on device /dev/sda1) has only 978 MiB (26%) space remaining (out of 3.7 GiB). You should really consider cleaning up some space!
3:
status: ERROR
summary: The root filesystem only has a total of 3.9 GiB which is quite worrisome! You will likely run out of disk space very quickly! It's recommended to have at least 16 GB for the root filesystem.
8:
description: System configurations
id: regenconf*hostname*
items:
status: SUCCESS
summary: All configuration files are in line with the recommended configuration!
9:
description: Applications
id: apps
items:
status: SUCCESS
summary: All installed apps respect basic packaging practices
now I can ping 192.168.1.167 but not my_local_domain.local
have still accesing issue https://my_local_domain.local/rss with This site can’t be reached ***.local’s DNS address could not be found. Diagnosing the problem. DNS_PROBE_POSSIBLE
Personal opinion: do not do that. Ever.
I am talking about LLM (Large Logorrhea Manufacturers) that you want to call Artificial Intelligence.
They dissolve your discourse in a bloated mess of synonyms (when you would need to use the actual technical word).
Full stop. This should have been the initial error to show, and a description like “I cannot reach my .local domain”.
.local domains work with the mDNS protocol. For it to work, your network needs to be able to multicast. This is usually not possible between a VM and its host.
Jarod is on the right path. You need to edit your hosts’ hosts file or to check your network capabilities.
Can you share the output of sudo ip a from your host?
Thank you for this feedback, I think, I need to choose clearer titles next time. If you have any feedback for this usage -rather than above things- let me know please.
I’m glad to this additional feedback. Thank you @tituspijean for correcting me and placing things on the right order. I’ve failed to recognize this meaning on the guide with the acknowledgement hints. I’m sorry that missing.
I think, I’ve to find more appropriate correction tool that not causing a ambiguity mess for ESL persons. Thanks for titling recommendation btw.
wow, I didn’t know mDNS and its working mechanism require a special attention and forwarding for VM and host machine itself.
Host’s host IP table
name@shaky:~$ sudo ip a
[sudo] password for shaggy:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 80:d0:f0:0f:bc:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.175/24 brd 192.168.1.255 scope global dynamic noprefixroute enp6s0
valid_lft 2031sec preferred_lft 2031sec
inet6 fe00::8c7c:0d00:a006:faf/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 00:40:ec:db:e0:cd brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
here additionally my VM server ip table
xemilian@hostname.local:~$ sudo ip a
[sudo] password for xemilian:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:07:0d:0a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.167/24 brd 192.168.1.255 scope global dynamic enp0s3
valid_lft 2816sec preferred_lft 2816sec
inet6 fe00::a00:00ff:fe07:0d0a/64 scope link
valid_lft forever preferred_lft forever
Additionally, I’ve searched this scenario after learned mDNS’s aspect. Providing access with hostname instead of IP’s for making possible to multicast between them. That’s amazing. I tried few things, I think maybe make it possible to find the correct adjustment;
I set bridge connection already. I’ve changed VM’s connection setting: Promiscuous mode : Deny → Allow All for full traffic throughput.
I enabled ufw -it did not- and set allow 80/tcp and allow 443/tcp options.
Set sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT
I saved this iptable reproducible usage after reboot sudo iptables-save | sudo tee /etc/iptables/iptables.rules
After these adjusmetnts, I can still ping 192.168.1.167 and access via ip not with my_hostname.local
but feel free to write in French 
if you’re more comfortable!