All Activity

How to import qcow2 to proxmox Importing qcow2 to Proxmox is an easy process that can be accomplished by following the simple steps below: Step 1 - Create a VM without an operating system First, when creating a Proxmox virtual machine, please note the following three key points: 1. Virtual Machine ID (VM ID): When creating a virtual machine, assign a unique VM ID. Keep this ID in mind as it will be used later. VM ID 187 is used in the image. 2. The operating system selects "Do Not Use Any Media": This means that the virtual machine will not boot from any media such as a CD-ROM or ISO file. This is because a qcow2 image will be imported later as the virtual hard disk. 3. Disk: You need to delete the default disk (click on the trash icon in the picture) The interface after deletion is shown below The rest is configured according to the needs of the VM operating system, the following is a general overview of the 187 VM. Then click Finish. Step 2 - Create a directory to store qcow2 images Create a directory for storing qcow2 images, the following is an example of creating a directory named "qcow" in the Proxmox default storage directory: 1. Click host > hit Shell > type the following command: sudo mkdir <directory_path> sudo mkdir /var/lib/vz/template/qcow Step 3 - Copy qcow2 mirror Copy the qcow2 image to the created "qcow" directory,type the following script: sudo cp <source_path> <destination_path> sudo cp /mnt/pve/Proxmox_NFS/images/33333/vm-33333-disk-0.qcow2 /var/lib/vz/template/qcow/ You can use the following command to check if the files have been successfully copied to the target directory: ls -l <directory_path> ls -l /var/lib/vz/template/qcow/ Step 4 - Import a qcow2 image into a VM in Proxmox 1. Switch to the qcow2 image directory Use the cd command to switch to the qcow2 image directory based on the path to the directory you created earlier. cd <directory_path> cd /var/lib/vz/template/qcow/ 2. Import the qcow2 image To import the qcow2 image into the VM, we use the qm following command: qm importdisk <VM ID> <qcow2 image> <storage name> qm importdisk 187 /var/lib/vz/template/qcow/vm-33333-disk-0.qcow2 local-lvm Step 5 - Attache a qcow2 virtual disk to a VM 1. Click on the 187 VM created in step 1 > select the Hardware 2. On the right side, the newly imported qcow2 disk is presented as an unused disk. Select the Unused disk > click the Edit 3. Select the bus type VirtIO Block > click Add You will now see a new disk with bus type VirtIO attached to the VM. Step 6 - Change the Boot Order 1. In order for the virtual machine to boot from the newly added disk, the boot order must be changed. Choose VM > hit Options > double - click Boot Order 2. To boot from a new disk, the new disk must be at the top of the boot order window. Drag the newly added VirtIO disk to the top > select the checkbox > click OK Step 7 - Start the Virtual Machine Just choose VM > click Console < hit Start Now

Install and Configure Collabora CODE How to Install Collabora Collabora CODE is more straightforward to install than Nextcloud. Typically, Collabora prerequisites are installed when Nextcloud is installed. To install Collabora CODE, follow the steps below: Import the Collabora CODE signing key. cd /usr/share/keyrings sudo wget https://collaboraoffice.com/downloads/gpg/collaboraonline-release-keyring.gpg 2. Create a source file for the Collabora CODE package repository. sudo nano /etc/apt/sources.list.d/collaboraonline.sources 3. Add the following information to the file and save it. Open File: /etc/apt/sources.list.d/collaboraonline.sources ---------------------------------------------------------------------------------------------------------------------------------------------- Types: deb URIs: https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-ubuntu2204 Suites: ./ Signed-By: /usr/share/keyrings/collaboraonline-release-keyring.gpg 4. Update the repository. sudo apt update -y 5. Install Collabora CODE using apt. sudo apt install coolwsd code-brand -y How to Configure Collabora Collabora configuration depends on an XML file at /etc/coolwsd/coolwsd.xml. Although this file can be edited directly, it is faster to use the coolconfig tool to make configuration changes. To configure Collabora, follow the steps below: With the current configuration, the coolwsd service continues to fail and restart. This happens because Collabora cannot establish an HTTPS connection with the local host. Use the coolconfig tool to disable HTTPS on the connection. sudo coolconfig set ssl.enable false sudo coolconfig set ssl.termination true 2. Only certain designated hosts are allowed to access the Collabora server. To designate Nextcloud as a trusted client, set storage.wopi.host to the Nextcloud domain, for example, nextcloud.example.com. In the following command, substitute the real domain name in place of example.com. sudo coolconfig set storage.wopi.host nextcloud.example.com 3. Create an administration account and provide a password for the account. When prompted, enter the admin username. Then, enter the admin password twice. sudo coolconfig set-admin-password 4. Restart the coolwsd service and verify the service status. sudo systemctl restart coolwsd sudo systemctl status coolwsd coolwsd.service - Collabora Online WebSocket Daemon Loaded: loaded (/lib/systemd/system/coolwsd.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-12-13 14:42:09 UTC; 7s ago How to Configure the Collabora Virtual Host 1. Install nginx. sudo apt install nginx 2. Create a collabora NGINX virtual host file. sudo vi /etc/nginx/sites-available/collabora 3. Add the following configuration to the file. Change the value of server_name from collabora.example.com to the name of the Collabora subdomain. Open File: /etc/nginx/sites-available/collabora ------------------------------------------------------------------------------------------------------------------------------------------- server { listen 80; listen [::]:80; server_name collabora.example.com; error_log /var/log/nginx/collabora.error; # static files location ^~ /browser { proxy_pass http://127.0.0.1:9980; proxy_set_header Host $http_host; } # WOPI discovery URL location ^~ /hosting/discovery { proxy_pass http://127.0.0.1:9980; proxy_set_header Host $http_host; } # Capabilities location ^~ /hosting/capabilities { proxy_pass http://127.0.0.1:9980; proxy_set_header Host $http_host; } # main websocket location ~ ^/cool/(.*)/ws$ { proxy_pass http://127.0.0.1:9980; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $http_host; proxy_read_timeout 36000s; } # download, presentation and image upload location ~ ^/(c|l)ool { proxy_pass http://127.0.0.1:9980; proxy_set_header Host $http_host; } # Admin Console websocket location ^~ /cool/adminws { proxy_pass http://127.0.0.1:9980; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $http_host; proxy_read_timeout 36000s; } } 4. Enable the Collabora site on the server by creating a symbolic link in the sites-enabled directory. sudo ln -s /etc/nginx/sites-available/collabora /etc/nginx/sites-enabled/collabora 5. Test the file syntax to ensure it does not contain any errors. sudo nginx -t 6. Restart NGINX and verify its status. sudo systemctl reload nginx sudo systemctl status nginx How to Enable HTTPS for the Collabora Domain Follow the installation of an SSL cert in the following article. https://kc-linux.com/index.php?/topic/81-how-to-secure-nginx-with-lets-encrypt-on-ubuntu-2404/ How to Connect Collabora to Nextcloud To use Collabora as a Nextcloud application, connect the Collabora server to Nextcloud via the Nextcloud Hub. Within the Nextcloud context, Collabora CODE is named “Nextcloud Office”. To attach Collabora to Nextcloud, follow the steps below: Navigate to the address of the Nextcloud domain and log in to NextCloud using your credentials. Click on the administrator profile, represented by a circle in the upper right-hand corner of the window and choose + Apps to view the applications panel. 3. On the applications panel, click the link for Office & text on the left-hand side navigation panel. 4. The subsequent page displays all the office and document management applications. Scroll through the list or use the search function to find the Nextcloud Office application. Click the Download and enable button beside the application. 5. Open the administrator profile by again clicking on the circle on the upper right of the screen. Select the Administration settings link. 6. On the left-hand side navigation panel, scroll down until the Nextcloud Office setting appears and click the label. 7. Nextcloud displays the Nextcloud Office settings. Enable the Use your own server setting by clicking the radio button. This reveals a text box for entering the URL (and Port) of Collabora Online-server. Enter the Collabora subdomain here, for example, https://collabora.example.com and click Save. If the connection is successful, Nextcloud confirms the Collabora Online server is reachable. 8. Locate the Advanced Settings section further down the page. Make sure the Use Office Open XML (OOXML) instead of OpenDocument Format by default for next files checkbox is checked. This ensures all files are compatible with Microsoft Office. For added security, enter the name of the Collabora domain name beside Allow list for WOPI requests. Conclusion Collabora is a free open-source office suite application that is an alternative to Microsoft Office. It is typically embedded as an application within Nextcloud, but other configuration options are available. Add the Linux package and use apt to install Collabora. Use the coolconfig utility to configure Collabora and then add a virtual host for the application. To integrate Collabora into Nextcloud, connect it using the Nextcloud Hub.

First, you'll need to install CIFS utilities on PBS: sudo apt install cifs-utils Create a folder that you will mount the remote SMB share into: mkdir /mnt/somefolder Create a credentials file to store the credentials to access the remote machine: nano /etc/samba/.smbcreds and set the username and password: username=smb_username password=smb_password Save your file and make it readable by root only: chmod 400 /etc/samba/.smbcreds Finally, mount your SMB share in PBS: sudo mount -t cifs -o rw,vers=3.0,credentials=/etc/samba/.smbcreds //1.2.3.4/sharename /mnt/somefolder Try to access the folder, and if it works attempt to write to it. If it works, make it auto-mount at boot by adding the following to /etc/fstab: nano /etc/fstab //1.2.3.4/sharename /mnt/somefolder cifs credentials=/etc/samba/.smbcred,uid=34,gid=34,defaults 0 0 Save the file. If for some reason something listed in /etc/fstab does not mount on reboot or if you made a change to it and need to test it, you can issue a mount -a to remount all shares. Note: you may or may not need the vers=3.0 option when mounting.I didn't need it, so if it doesn't work with try again without it. Also, the uid=34,gid=34 means that you are mounting this share as the backup user in PBS; as stated earlier in this thread that is a necessary to allowing PBS read/write access to the mount. The final step is adding your SMB share as a datastore in PBS. For that you simply use the GUI to Add Datastore and set the backup path to /mnt/somefolder and it should mount.

How to mount an external usb hard drive. 1. You need to get the disk information. run. lsbl Your output will look like this. In this example we are looking at sdb1 our 4 TB external drive. 2. We need to get the uuid of the drive. run. sudo blkid /dev/sdb1 your output will look like this. 3. Copy the UUID. 4. Open fstab sudo nano /etc/fstab Add the following to the bottom of the file. UUID=58DC2FFDDC2FD452 /mnt/wd-external auto nosuid,nodev,nofail,x-gvfs-show 0 0 It will look like this. 5. Save and close the file. 6. reboot server to verify drive mounts automatically.

sudo -u www-data php occ user:auth-tokens:list username sudo -u www-data php occ user:auth-tokens:delete username --last-used-before 2024-12-05T03:01:26+00:00

To install imagemagick run the following. sudo apt install php-imagick imagemagick

Nextcloud Error: The PHP OPcache module is not properly configured. The OPcache interned strings buffer is nearly full Modify the following: cat /etc/php/8.3/fpm/conf.d/99-custom.ini [opcache] opcache.interned_strings_buffer=64 opcache.memory_consumption=2048 restart apache sudo systemctl restart apache2.service Then restart php-fpm sudo systemctl restart php8.3-fpm.service

How to resolved the following error. ERROR: Some headers are not set correctly on your instance - The `Strict-Transport-Security` HTTP header is not set (should be at least `15552000` seconds) Add the following <IfModule mod_headers.c> Header always set Strict-Transport-Security "max-age=15552000; > </IfModule> New version: <IfModule mod_headers.c> Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains" </IfModule> It should look like this when complete. restart apache server. The error should be gone.

How to install AdGuard Home to RHEL/CentOS/Alma/Rocky 1. https://github.com/AdguardTeam/AdGuardHome#getting-started 2. Install using wget. wget --no-verbose -O - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v 3. Add firewall rules to access AdGuard. firewall-cmd --permanent --add-port=3000/tcp firewall-cmd --reload firewall-cmd --list-all 4. Add firewall rules to access the AdGuard webserver. firewall-cmd --permanent --add-port=3000/tcp firewall-cmd --reload firewall-cmd --list-all 5. Navigate to local server IP. http://192.168.x.x:3000 to complete installation.

To install adguard as a proxmox container. 1. download container server Ubuntu, Alpine, etc.. 2.run one of the following. Automated install (Linux/Unix/MacOS/FreeBSD/OpenBSD) To install with curl run the following command: curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v To install with wget run the following command: wget --no-verbose -O - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v To install with fetch run the following command: fetch -o - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v The script also accepts some options: -c <channel> to use specified channel; -r to reinstall AdGuard Home; -u to uninstall AdGuard Home; -v for verbose output.

To upgrade Authentik you need to download the new compose file. Login to docker server and navigate to /var/dockers/authentik run sudo wget -O docker-compose.yml https://goauthentik.io/version/2024.4/docker-compose.yml Next we need to change the ports in the docker-compose.yml. by default http port is 9000 which is the same port that portainer uses. Change to 9100. sudo nano docker-compose.yml docker compose pull docker compose up -d