NethServer Version: NS8beta, fresh updated
Module: Dokuwiki
I installed Dokuwiki via SW-Center and created an DNS-alias “wiki.myhome.domain.tld” corresponding to the Dokuwiki-Settings, section “Wiki FQDN”.
If I use the FQDN to start Dokuwiki I get the error “bad gateway”.
Sincerelly, Marko
how much time, this messages is done either when the service fails to start, or when the service has not yet started, sometimes you have to wait
can you grep failure : journalctl _UID=$(id -u dokuwiki1)
adapt dokuwiki1 to your MODULE_ID
Best regards, Marko
btw: NextCloud works fine.
How did you install ns8 ?
The first donuwiki module installed is dokuwiki1, the next dokuwiki2
You can find the module_ID by doing ls /home you will see the home of the linux user running your module
We need to check logs and understand why the service did not start
I installed it using the manual on Debian starting with the first alpha and upgraded to the current beta.
…virtualized within Proxmox.
I don’t have access to ssh console.
Check the /etc/ssh/sshd_config file to allow root to connect and restart ssh
A blind shot of course
I’m sorry, how can I check out without access to ssh console?
By the web console of the proxmox vm or the real console of your server
Probably the log panel of the ns8 could help also but to help development it is easier to check it by ssh
In Proxmox, click the “Console” button of the VM" and login with root, then:
echo 'PermitRootLogin yes' >> /etc/ssh/sshd_config
systemctl restart sshd
systemctl status sshd
Then from remote console, try login with root.
Michel-André
Yes, I know this. But all permissions are rejected.
As I wrote, no login possible with root / admin and standard password (Nethesis,1234) also not after changing this within Settings/Account.
…also not with my individual created admin user
Login via web browser on node1 is possible.
Hi Michel, forgive me, but I’m totally confused. Servermanger (980/9090) in NS8?
I thought their life cycle ended with NS7.
Incredulous, I tried it anyway: https://ns8beta.home.mydomain.tld:980 or 9090
I was actually not surprised that this did not work.
Best regards, Marko
however, a page is not loaded through these ports.
Alpha? It’s not possible to upgrade from alpha.
We are responsible for a lot but if you cannot login to the console of the server or you cannot ssh these are handled by the debian distribution and not the ns8 layers
Thynk you. I will reinstall.
In this case I remembered wrongly
I installed in new on top of Debian 12.
At the end of the installation I got messages:
Installing collected packages: resolvelib, pyasn1, ptyprocess, lockfile, typing-extensions, semver, regex-engine, PyYAML, pycparser, psutil, pexpect, packaging, multidict, MarkupSafe, ldap3, hiredis, frozenlist, docutils, dnspython, async-timeout, yarl, redis, python-daemon, Jinja2, cffi, aiosignal, aioredis, pycares, cryptography, brotlipy, ansible-runner, aiohttp, ansible-core, aiodns
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.3 PyYAML-6.0 aiodns-3.0.0 aiohttp-3.8.4 aioredis-2.0.1 aiosignal-1.3.1 ansible-core-2.15.1 ansible-runner-2.3.1 async-timeout-4.0.2 brotlipy-0.7.0 cffi-1.15.1 cryptography-41.0.1 dnspython-2.3.0 docutils-0.20 frozenlist-1.4.0 hiredis-2.2.3 ldap3-2.9.1 lockfile-0.12.2 multidict-6.0.4 packaging-23.0 pexpect-4.8.0 psutil-5.9.4 ptyprocess-0.7.0 pyasn1-0.4.8 pycares-4.3.0 pycparser-2.21 python-daemon-3.0.1 redis-4.5.5 regex-engine-1.1.0 resolvelib-1.0.1 semver-3.0.1 typing-extensions-4.6.3 yarl-1.9.2
Setup registry:
Add firewalld core rules:
Write initial cluster environment state
Generating a new RSA key pair for SSH:
Generating public/private rsa key pair.
Your identification has been saved in /root/.ssh/id_rsa
Your public key has been saved in /root/.ssh/id_rsa.pub
The key fingerprint is:
SHA256:iS5t<snipp>QAY root@NS8Beta
The key's randomart image is:
+---[RSA 3072]----+
|EB+*+o+oo |
<snipp>
| . ... |
+----[SHA256]-----+
Adding id_rsa.pub to module skeleton dir:
Add /etc/hosts entries:
Generate WireGuard VPN key pair:
wwqnKbK3wm+/doQMmjgsYlsVXoXS83DKNm+b7/00zzc=
Start Redis DB:
Created symlink /etc/systemd/system/default.target.wants/redis.service → /etc/systemd/system/redis.service.
Generating cluster password:
Generating api-server password:
Generating node password:
AUTH failed: WRONGPASS invalid username-password pair or user is disabled.
OK
OK
3
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Start API server and core agents:
Created symlink /etc/systemd/system/multi-user.target.wants/api-server.service → /etc/systemd/system/api-server.service.
Created symlink /etc/systemd/system/default.target.wants/agent@cluster.service → /etc/systemd/system/agent@.service.
Created symlink /etc/systemd/system/default.target.wants/agent@node.service → /etc/systemd/system/agent@.service.
Grant initial permissions:
Install Traefik:
<7>podman-pull-missing ghcr.io/nethserver/traefik:1.1.0
Trying to pull ghcr.io/nethserver/traefik:1.1.0...
Error: initializing source docker://ghcr.io/nethserver/traefik:1.1.0: reading manifest 1.1.0 in ghcr.io/nethserver/traefik: manifest unknown
Traceback (most recent call last):
File "/usr/local/agent/bin/podman-pull-missing", line 35, in <module>
subprocess.run(['podman', 'pull', image_url]).check_returncode()
File "/usr/lib/python3.11/subprocess.py", line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '['podman', 'pull', 'ghcr.io/nethserver/traefik:1.1.0']' returned non-zero exit status 125.
Traceback (most recent call last):
File "/var/lib/nethserver/cluster/actions/add-module/50update", line 78, in <module>
agent.run_helper('podman-pull-missing', image_url, progress_callback=agent.get_progress_callback(0,33)).check_returncode()
File "/usr/lib/python3.11/subprocess.py", line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
subprocess.CalledProcessError: Command '('podman-pull-missing', 'ghcr.io/nethserver/traefik:1.1.0')' returned non-zero exit status 1.
I don’t know if that has any significance:
Generating node password:
AUTH failed: WRONGPASS invalid username-password pair or user is disabled.
It’s not possible to start cluster-admin, because connection to the url (FQDN or IP) is impossible.