Reytech reytech-dev

Steps to fix "error file '/boot/vmlinux-x.x-x86_64' not found (Manjaro)

Change UEFI Settings on your broken system: Boot > Secure Boot > Other OS (You can also disable UEFI, but make sure to re-enable it after you are done here!!)
Boot broken system with the live-system

$ firewall-cmd --get-active-zones

$ sudo firewall-cmd --zone=docker --change-interface=docker0

If "docker" zone is available, change interface to docker0 (persisted, thanks rbjorklin)

Mount an encrypted partition on boot

Hint: Always replace "< .... >" with the actual value

$ lsblk

Example configuration

location /example {
  set $exampleVariable "examplePath";
  proxy_pass http://localhost:8080/$exampleVariable;
}

The following instructions where tested with ubuntu 20.04.

The following module builds of kdeconnect-app will fail with the given instructions (so far, will update the gist asap I found out whats missing):

This issue is mostly caused through a failed kernel update. So far I experienced it only if the yum update transaction got interrupted.

(tested with CentOS 7 and a Digital Ocean droplet)

	<?php
	/**
	* Generates a 42 chars random string (No need to change it)
	*/
	$oauth_nonce = preg_replace("/[^A-Za-z0-9 ]/", "", base64_encode(random_bytes(32)));
	/**
	* Get current unix timestamp (careful what is set as Locale in your PHP environment - No need to change it)
	*/
	$oauth_timestamp = time();
	/**

	<?php
	////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
	// This script is made and tested for GET requests, please change the required params for other types of requests //
	////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

	// e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - sha256 of empty input
	date_default_timezone_set("UTC");
	// Region where the space is hosted (amsterdam)
	$region = "ams3";
	// Host of the space without protocol

	Source: https://stackoverflow.com/questions/40214617/docker-no-route-to-host

	# Firewalld settings
	1. open all IPs starts with "172" so that all the containers may communicate each other
	```shell
	$ sudo firewall-cmd --permanent --zone=public --add-rich-rule='rule family=ipv4 source address=172.0.0.0/8 accept'
	```

	2. make our container able to visit the network outside
	```shell

	#!/bin/bash
	set -o errexit

	clear
	printf "\n* This script will download a cloud image and create a Proxmox VM template from it. *\n\n"

	### HOW TO USE
	### Pre-req:
	### - run on a Proxmox 6 server
	### - a dhcp server should be active on vmbr1