Just another WordPress site
https://youtu.be/4isEhE2rvmA?si=yR8BRSAjJvc56H4S
Gute Anleitung hier, jedoch funktionierte es noch nicht.
Fehler gab es bei den Zahlen in der cgroup2 config.
Aktuelle Version (06.01.2025) – https://download.nvidia.com/XFree86/Linux-x86_64/550.142/
Weitere URL für das Archiv – https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
URL des Proxmox Helper Scripts – https://community-scripts.github.io/ProxmoxVE/scripts?id=plex
Lösung:
|
1 2 3 |
ALT + F3 ps ax | grep traceroute kill -9 <pid> vom traceroute |
wahlweise Netzwerkkabel ziehen
nächster Fehler:
https://forum.proxmox.com/threads/generic-solution-when-install-gets-framebuffer-mode-fails.111577/
danach noch Probleme gehabt mit der eMail Eingabe (keine Möglichkeit gehabt das @ Zeichen einzutippen).
Zurück -> Vorwärts und die default Mail editiert.
|
1 |
badblocks -wsv -b 4096 -c 8192 -t random -o ~/badblocks-output.txt /dev/sdb |
|
1 |
smartctl -t long /dev/hdX |
Crowdsec Install
|
1 |
root@OPNsense:/usr/local/etc/crowdsec # nano config.yaml |
|
1 2 3 4 5 |
prometheus: enabled: true level: full listen_addr: 127.0.0.1 listen_port: 6060 |
Anpassung der listen_addr
Restart
Besagte IP in der Prometheus als Endpoint eintragen. Restart crowdsec.
Dashboards https://github.com/crowdsecurity/grafana-dashboards
|
1 |
'overwriteprotocol' => 'https', |
Fix: “Could not open input file: artisan”
If you see the following error when running php artisan in your Snipe-IT container:
|
1 |
Could not open input file: artisan |
You are likely in the wrong directory. Navigate to the application root first:
|
1 2 |
<span class="token token">cd</span> /app/www <span class="token token">chmod</span> +x artisan |
Then run your command again. For example, to create the initial admin user:
|
1 2 3 4 5 6 7 8 9 10 11 |
php artisan snipeit:create-admin <span class="token token">\</span> --first_name<span class="token token">=</span>buyenne <span class="token token">\</span> --last_name<span class="token token">=</span>buyenne <span class="token token">\</span> --email<span class="token token">=</span>mail@example.com <span class="token token">\</span> --username<span class="token token">=</span>admin <span class="token token">\</span> --password<span class="token token">=</span>xxxxxxxx ``<span class="token token">`</span> **Expected output:** <span class="token token">`</span>`` New user created |
Update 2026: this setup has since been upgraded to Redmine 6.1 on PostgreSQL 15, and the permission workaround below is no longer needed. See Upgrading a neglected Redmine: PostgreSQL 9.6 → 15 and Redmine 5.0 → 6.1 in Docker.
I had an old Redmine backup from 2017 lying around and wanted it running again on a current system. This is a quick record of how I restored it with the sameersbn Docker images, and the permission problem that kept getting in the way.
In der cmdline.txt die Werte für die IP Konfig eintragen:
ip=<Raspi-ip>:<Netboot-ip>:<Gateway-ip>:<Subnetzmaske>:<Hostname>:<Netzwerkkarte>:<Autoconf>
Anschließend noch ssh Server aktivieren. Einfach eine Leerdatei ssh im selben Ordner erstellen.