christianlempa/videos

This is my video documentation. Here you'll find code-snippets, technical documentation, templates, command reference, and whatever is needed for all my YouTube Videos.

Christian's "Videos"

Hey, there!

I’m Christian, and I’m passionate about creating educational tech content for IT Pros and Homelab nerds.

This Repository Video is my video documentation. Here you'll find code-snippets, technical documentation, templates, command reference, and whatever is needed for all my YouTube Videos.

⚠️ Be aware, products can change over time. I do my best to keep up with the latest changes and releases, but please understand that this won’t always be the case.

I created them as free resources to be used in your specific use cases. If you're searching for detailed, in-depth tutorials on some tools or technologies, check out my YouTube Channel.

Contribution

If you’d like to contribute to this project, reach out to me on social media or Discord, or create a pull request for the necessary changes.

Other Resources

• Dotfiles - My personal configuration files on macOS
• Boilerplates - Templates for various projects like Docker, K8S, Ansible, etc
• Cheat-Sheets - Command Reference for various tools and technologies
• Videos - Documentation and project files for all my video tutorials on YouTube
• Homelab - This is my entire Homelab documentation, and configurations for infrastructure, applications, networking, and more.

Support me

Creating high-quality videos and valuable resources that are accessible to everyone, free of charge, is a huge challenge. With your contribution, I can dedicate more time and effort into the creation process, which ultimately enhances the quality of the content. So, all your support, by becoming a member, truly makes a significant impact on what I do. And you’ll also get some cool benefits and perks in return, as a recognition of your support.

Remember, supporting me is entirely optional. Your choice to become a member or not won't change your access to my videos and resources. You are also welcome to reach out to me on Discord, if you have any questions or feedback.

https://www.patreon.com/christianlempa

videos's Issues

Nginx tutorial foult

Hi

I dont know what im doing wrong but i cant login , plz help! I`m on Ubuntu server , portainer , and try to start nginx

NGINX Reverse Proxy Config for Teleport Docker container

Dear Christian,

thanks a lot for your tutorials in this toppic! Great to see others be enthusiastic about teleport :)

I also have a homelab running on proxmox and Nginx reverse Proxy and have several Services running on it, so I simply cant use port 443 by default like you described. I´d like to pass it through the Reverse proxy butcant get it to work. I always get the error

WARN [MX:PROXY:] "\nERROR REPORT:\nOriginal Error: *trace.BadParameterError multiplexer failed to detect connection protocol

Based on this post, I´ve edited the teleport.yml file to this:

#version: v2
teleport:
  nodename: teleport
  data_dir: /var/lib/teleport
  log:
    output: stderr
    severity: INFO
    format:
      output: text
  ca_pin: ""
  diag_addr: ""
auth_service:
  enabled: "yes"
  listen_addr: 0.0.0.0:3025
#  proxy_listener_mode: multiplex
  cluster_name: teleport.example.com
ssh_service:
  enabled: "yes"
  commands:
  - name: hostname
    command: [hostname]
    period: 1m0s
proxy_service:
  enabled: "yes"
  web_listen_addr: 0.0.0.0:443
  public_addr: teleport.example.com:443
  https_keypairs: []
#  acme:
#    enabled: yes
#    email: <Email>

In the reverse Proxy I forwarded "teleport.example.com" as https Protokoll to my host-IP on port 443

Can you explain how to configure the Reverse proxy or how to use teleport on another port?

; missing

in the bin9 docs in named.conf is a ";" after "192.168.0.0/24" missing.

acl internal {
  192.168.0.0/24;
};

By the way: Thank you for your excellent videos and proper documentation!

Portainer Install Ubuntu tutorial

Under section 1.1 I was getting some depercation warning. Im new to linux but I did find that the apt-key now uses keyrings as the latest version of Ubuntu 22.04 is the last version to support the older key types
I found this https://docs.docker.com/engine/install/ubuntu/

I already had the folder so the first line I didnt need

Is this the right thing to do?

docker-compose up -d not working

root@raspberrypi:~/nginxproxymanager# docker-compose up -d
/usr/local/bin/docker-compose: line 1: Not: command not found

ansible-semaphore

Throwing following error while configuring using example docker-compose.yaml file.

ERROR: The Compose file './docker-compose.yaml' is invalid because:
Unsupported config option for services: 'mysql'
Unsupported config option for volumes: 'semaphore-mysql'

What if client will be Windows?

Whats the difference between Linux and Windows client configuration? Should the conf file look the same as on Linux? What should I do apart from editing the conf file? Any commands? Excuse me for this questions, I'm noobie in this topic.

ansiblesemaphore-tutorial : user setting in docker-compose.yaml

Hello! I just followed your tutorial and wanted to deploy semaphore via portainer stacks, but had issues with "user" setting in docker-compose.yaml. When manually specified UID and GUID it has issues starting, it started after I removed the user option.

So question is, what use has this "user" option for this container, was checking the official documentation and did not see this option set. Was it intended to run container as root? If yes why when it is not in the semaphore's docs (at least in the installation part, did't look deeper in the docs)

Thank you for clarification!

question: kubernetes at home

In your HA k3s video, there is an ASCII diagram in a markdown file at 08:36 i.e. image

May I know what tools you are using to create and show this ASCII diagram in the terminal?

Prometheus config file does not support current node exporter and cadvisor compose files

Both docker-compose.yml files of node-exporter and cAdvisor contain this line:
network_mode: host
which in turn invalidates the current boilerplate config of prometheus since

- targets: ['node_exporter:9100']
- targets: ['cadvisor:8080']

do not work with the host mode as they don't join the stacks network
I hope that was understandable and I double checked and figured my solution out:

- targets: ['<dockerhostIP>:9100']
- targets: ['<dockerhostIP>:8080']

More automatic way to generate certificates

Hi,

First, I want to thank you a lot for the explanations you provided in your multiple videos / cheatsheets about SSL. It drastically augmented my understanding about self-signed certificates, and for that I am very grateful to you.

Now, I would like to share with you another way to generate self-signed certificates on kubernetes with cert-manager that does not involve to write any openssl command. I find that way pretty cool and simple. Maybe you want to make a video about it sometime? It is very close to what you showed in your video:

1. you define the root cluster issuer (sorry my vocabulary on the topic might not be very precise, I'm still learning) like this

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: root-issuer
spec:
  selfSigned: {}

2. you define the root CA like this

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: root-ca
spec:
  isCA: true
  commonName: root-ca
  secretName: root-secret
  privateKey:
    algorithm: ECDSA
    size: 256
  issuerRef:
    name: root-issuer
    kind: ClusterIssuer
    group: cert-manager.io

3. you define the CA issuer as follows

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: ca-issuer
spec:
  ca:
    secretName: root-secret

4. you finally define your tls certificate like so

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: tls-certificate
spec:
  secretName: tls-secret
  issuerRef:
    name: ca-issuer
    kind: ClusterIssuer
  dnsNames:
    - "my-dns-name"

With that in place, I was able to achieve the very same result as you did in your video, without using openssl, but instead by using cert-manager's full power. The whole thing is documented here and here.

Docker problem

How solve this pls help me

Bind9 on Docker don't start

Hi Christian.
I try to install a docker with bind9.
I'm following all the steps (both from the video and from here on github), but I can't get Docker to start.
In the logs, I can see some "Permission denied" to read a files.
And in the last line "resolver priming query complete: failure".
And bind don't start.

Any clues?
Thank's a lot.

.
root@bind9:/docker# docker-compose up
[+] Running 1/0
⠿ Container bind9 Created 0.0s
Attaching to bind9
bind9 | Starting named...
bind9 | exec /usr/sbin/named -u "root" "-g" ""
bind9 | 23-Feb-2023 20:09:06.290 starting BIND 9.18.4-2ubuntu2.1-Ubuntu (Stable Release) id:
bind9 | 23-Feb-2023 20:09:06.290 running on Linux x86_64 5.15.85-1-pve #1 SMP PVE 5.15.85-1 (2023-02-01T00:00Z)
bind9 | 23-Feb-2023 20:09:06.290 built with '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-option-checking' '--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--runstatedir=/run' '--disable-maintainer-mode' '--disable-dependency-tracking' '--libdir=/usr/lib/x86_64-linux-gnu' '--sysconfdir=/etc/bind' '--with-python=python3' '--localstatedir=/' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--disable-static' '--with-gost=no' '--with-openssl=/usr' '--with-gssapi=yes' '--with-libidn2' '--with-json-c' '--with-lmdb=/usr' '--with-gnu-ld' '--with-maxminddb' '--with-atf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-aaaa' '--disable-native-pkcs11' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -ffile-prefix-map=/build/bind9-9eyUWq/bind9-9.18.4=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE' 'LDFLAGS=-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
bind9 | 23-Feb-2023 20:09:06.294 running as: named -u root -g
bind9 | 23-Feb-2023 20:09:06.294 compiled by GCC 12.2.0
bind9 | 23-Feb-2023 20:09:06.294 compiled with OpenSSL version: OpenSSL 3.0.5 5 Jul 2022
bind9 | 23-Feb-2023 20:09:06.294 linked to OpenSSL version: OpenSSL 3.0.5 5 Jul 2022
bind9 | 23-Feb-2023 20:09:06.294 compiled with libxml2 version: 2.9.14
bind9 | 23-Feb-2023 20:09:06.294 linked to libxml2 version: 20914
bind9 | 23-Feb-2023 20:09:06.294 compiled with json-c version: 0.16
bind9 | 23-Feb-2023 20:09:06.294 linked to json-c version: 0.16
bind9 | 23-Feb-2023 20:09:06.294 compiled with zlib version: 1.2.11
bind9 | 23-Feb-2023 20:09:06.294 linked to zlib version: 1.2.11
bind9 | 23-Feb-2023 20:09:06.294 ----------------------------------------------------
bind9 | 23-Feb-2023 20:09:06.294 BIND 9 is maintained by Internet Systems Consortium,
bind9 | 23-Feb-2023 20:09:06.294 Inc. (ISC), a non-profit 501(c)(3) public-benefit
bind9 | 23-Feb-2023 20:09:06.294 corporation. Support and training for BIND 9 are
bind9 | 23-Feb-2023 20:09:06.294 available at https://www.isc.org/support
bind9 | 23-Feb-2023 20:09:06.294 ----------------------------------------------------
bind9 | 23-Feb-2023 20:09:06.294 found 4 CPUs, using 4 worker threads
bind9 | 23-Feb-2023 20:09:06.294 using 4 UDP listeners per interface
bind9 | 23-Feb-2023 20:09:06.298 config.c: option 'trust-anchor-telemetry' is experimental and subject to change in the future
bind9 | 23-Feb-2023 20:09:06.302 loading configuration from '/etc/bind/named.conf'
bind9 | 23-Feb-2023 20:09:06.302 unable to open '/etc/bind/bind.keys'; using built-in keys instead
bind9 | 23-Feb-2023 20:09:06.314 looking for GeoIP2 databases in '/usr/share/GeoIP'
bind9 | 23-Feb-2023 20:09:06.318 using default UDP/IPv4 port range: [32768, 60999]
bind9 | 23-Feb-2023 20:09:06.318 using default UDP/IPv6 port range: [32768, 60999]
bind9 | 23-Feb-2023 20:09:06.318 listening on IPv4 interface lo, 127.0.0.1#53
bind9 | 23-Feb-2023 20:09:06.326 listening on IPv4 interface eth0, 172.18.0.2#53
bind9 | 23-Feb-2023 20:09:06.326 Could not open '//run/named/named.pid'.
bind9 | 23-Feb-2023 20:09:06.326 Please check file and directory permissions or reconfigure the filename.
bind9 | 23-Feb-2023 20:09:06.326 could not open file '//run/named/named.pid': Permission denied
bind9 | 23-Feb-2023 20:09:06.326 generating session key for dynamic DNS
bind9 | 23-Feb-2023 20:09:06.326 Could not open '//run/named/session.key'.
bind9 | 23-Feb-2023 20:09:06.326 Please check file and directory permissions or reconfigure the filename.
bind9 | 23-Feb-2023 20:09:06.326 could not open file '//run/named/session.key': Permission denied
bind9 | 23-Feb-2023 20:09:06.326 could not create //run/named/session.key
bind9 | 23-Feb-2023 20:09:06.326 failed to generate session key for dynamic DNS: permission denied
bind9 | 23-Feb-2023 20:09:06.330 sizing zone task pool based on 1 zones
bind9 | 23-Feb-2023 20:09:06.330 none:98: 'max-cache-size 90%' - setting to 6994MB (out of 7771MB)
bind9 | 23-Feb-2023 20:09:06.330 using built-in root key for view _default
bind9 | 23-Feb-2023 20:09:06.330 set up managed keys zone for view _default, file 'managed-keys.bind'
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 10.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 16.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 17.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 18.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 19.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 20.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 21.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 22.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 23.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.330 automatic empty zone: 24.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 25.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 26.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 27.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 28.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 29.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 30.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 31.172.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 168.192.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 64.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 65.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 66.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 67.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 68.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 69.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.354 automatic empty zone: 70.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 71.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 72.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 73.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 74.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 75.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 76.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 77.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 78.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 79.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 80.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 81.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 82.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 83.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 84.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 85.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 86.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.358 automatic empty zone: 87.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.362 automatic empty zone: 88.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 89.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 90.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 91.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 92.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 93.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 94.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 95.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 96.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 97.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 98.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.366 automatic empty zone: 99.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 100.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 101.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 102.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 103.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 104.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 105.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 106.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 107.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 108.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 109.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 110.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 111.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 112.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 113.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 114.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 115.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.370 automatic empty zone: 116.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 117.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 118.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 119.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 120.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 121.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 122.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 123.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 124.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 125.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 126.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 127.100.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 0.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 127.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 254.169.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 2.0.192.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 100.51.198.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.374 automatic empty zone: 113.0.203.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: D.F.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 8.E.F.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 9.E.F.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: A.E.F.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: B.E.F.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: EMPTY.AS112.ARPA
bind9 | 23-Feb-2023 20:09:06.378 automatic empty zone: HOME.ARPA
bind9 | 23-Feb-2023 20:09:06.382 configuring command channel from '/etc/bind/rndc.key'
bind9 | 23-Feb-2023 20:09:06.382 command channel listening on 127.0.0.1#953
bind9 | 23-Feb-2023 20:09:06.386 configuring command channel from '/etc/bind/rndc.key'
bind9 | 23-Feb-2023 20:09:06.386 command channel listening on ::1#953
bind9 | 23-Feb-2023 20:09:06.386 not using config file logging statement for logging due to -g option
bind9 | 23-Feb-2023 20:09:06.414 managed-keys-zone: loaded serial 9
bind9 | 23-Feb-2023 20:09:06.422 address not available resolving './NS/IN': 2001:500:12::d0d#53
bind9 | 23-Feb-2023 20:09:06.426 address not available resolving './NS/IN': 2001:500:1::53#53
bind9 | 23-Feb-2023 20:09:06.426 zone demo.home.es/IN: loaded serial 2022122800
bind9 | 23-Feb-2023 20:09:06.426 address not available resolving './NS/IN': 2001:7fe::53#53
bind9 | 23-Feb-2023 20:09:06.426 all zones loaded
bind9 | 23-Feb-2023 20:09:06.426 running
bind9 | 23-Feb-2023 20:09:06.426 address not available resolving './NS/IN': 2001:7fd::1#53
bind9 | 23-Feb-2023 20:09:06.426 address not available resolving './NS/IN': 2001:500:9f::42#53
bind9 | 23-Feb-2023 20:09:06.426 address not available resolving './NS/IN': 2001:dc3::35#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:503:ba3e::2:30#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:503:c27::2:30#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:500:2::c#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:500:a8::e#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:500:2d::d#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:500:2f::f#53
bind9 | 23-Feb-2023 20:09:06.430 address not available resolving './NS/IN': 2001:500:200::b#53
bind9 | 23-Feb-2023 20:09:06.434 SERVFAIL unexpected RCODE resolving './NS/IN': 192.112.36.4#53
bind9 | 23-Feb-2023 20:09:06.438 SERVFAIL unexpected RCODE resolving './NS/IN': 198.97.190.53#53
bind9 | 23-Feb-2023 20:09:06.438 SERVFAIL unexpected RCODE resolving './NS/IN': 192.36.148.17#53
bind9 | 23-Feb-2023 20:09:06.442 managed-keys-zone: No DNSKEY RRSIGs found for '.': success
bind9 | 23-Feb-2023 20:09:06.446 SERVFAIL unexpected RCODE resolving './NS/IN': 193.0.14.129#53
bind9 | 23-Feb-2023 20:09:06.450 SERVFAIL unexpected RCODE resolving './NS/IN': 199.7.83.42#53
bind9 | 23-Feb-2023 20:09:06.454 SERVFAIL unexpected RCODE resolving './NS/IN': 202.12.27.33#53
bind9 | 23-Feb-2023 20:09:06.458 SERVFAIL unexpected RCODE resolving './NS/IN': 198.41.0.4#53
bind9 | 23-Feb-2023 20:09:06.462 SERVFAIL unexpected RCODE resolving './NS/IN': 192.58.128.30#53
bind9 | 23-Feb-2023 20:09:06.466 SERVFAIL unexpected RCODE resolving './NS/IN': 192.33.4.12#53
bind9 | 23-Feb-2023 20:09:06.470 SERVFAIL unexpected RCODE resolving './NS/IN': 192.203.230.10#53
bind9 | 23-Feb-2023 20:09:06.474 SERVFAIL unexpected RCODE resolving './NS/IN': 199.7.91.13#53
bind9 | 23-Feb-2023 20:09:06.478 SERVFAIL unexpected RCODE resolving './NS/IN': 192.5.5.241#53
bind9 | 23-Feb-2023 20:09:06.482 SERVFAIL unexpected RCODE resolving './NS/IN': 199.9.14.201#53
bind9 | 23-Feb-2023 20:09:06.482 resolver priming query complete: failure

resolver priming query complete: failure

In the bind9-docker-compose guide

in the first with the documentation and without any zone created when i start the container i get this output

in terminal after running docker compose up

bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.58.128.30#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.58.128.30#53 bind-9 | 19-Apr-2023 14:45:02.132 DNS format error from 192.112.36.4#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 14:45:02.132 FORMERR resolving './NS/IN': 192.112.36.4#53 bind-9 | 19-Apr-2023 14:45:02.132 resolver priming query complete: failure

in my system terminal running nslookup

~ nslookup youtube.com 22.10.20.46
Server: 22.10.20.46
Address: 22.10.20.46#53

** server can't find youtube.com: SERVFAIL

in terminal after running nslookup

bind-9 | 19-Apr-2023 14:48:58.043 address not available resolving 'com/DS/IN': 2001:503:ba3e::2:30#53 bind-9 | 19-Apr-2023 14:48:58.043 broken trust chain resolving 'youtube.com/A/IN': 1.1.1.1#53

Then i added dnssec-validation no in named.conf

in terminal after running docker compose up

ind-9 | 19-Apr-2023 15:00:46.429 managed-keys-zone: loaded serial 0 bind-9 | 19-Apr-2023 15:00:46.441 all zones loaded bind-9 | 19-Apr-2023 15:00:46.441 running

in my system terminal running nslookup

~ nslookup youtube.com 22.10.20.46
Server: 22.10.20.46
Address: 22.10.20.46#53

Non-authoritative answer:
Name: youtube.com
Address: 142.250.66.14

in terminal after running nslookup

bind-9 | 19-Apr-2023 15:02:30.908 DNS format error from 198.97.190.53#53 resolving ./NS for <unknown>: non-improving referral bind-9 | 19-Apr-2023 15:02:30.908 FORMERR resolving './NS/IN': 198.97.190.53#53 bind-9 | 19-Apr-2023 15:02:30.908 resolver priming query complete: failure

the nslookup seams to be working but the output looks like something is wrong somewhere

Great terraform video

https://www.youtube.com/watch?v=fEIIxZUf4co

To be honest, I felt like thinking "What is this all aiming towards??" throughout a large part of the video! 😅

But then it all came together right at the end, specifically 29:18 - 29:38 (https://www.youtube.com/watch?v=fEIIxZUf4co&t=1759s)

"And you can this... this is now working. We are logged into our server.
"This probably took like, hmm, a few seconds to deploy this cloud instance? So this is pretty cool. You can see what you can do with that; Terraform is very, very powerful to dynamically provision infrastructure this way."

Those 20 seconds copied right at the start of the video as like a "teaser" (maybe you are not into that style) would be very helpful, tutorial-wise. It lets me know what your goal is and, from your genuine reaction of being pleasantly surprised, how worthwhile my attention should be to the subject.

Great video, thanks for the content. I will watch more and share.

Existing NPM

Thanks for your great videos. I already have NPM running, you mention this scenario briefly but never talk about ports that have to be setup on the nextcloud-app... am I missing something?

mailserver.conf

page: https://github.com/christianlempa/videos/tree/main/mailcow-tutorial

correct: mailcow.conf

wrong: mailserver.conf

---

some feedback to your video:

It did not work. Port 443 is occupied by my Nginx. And I suspect there will be MX Record problems. In addition, my web server with 2 vCPU 4 GB (df.eu VPS) became almost unusable. I am currently paying €4 per month for my email address and am looking for a solution.

videos/truenasscale-traefik

After a recent update to the TrueCharts Traefik application this method no longer works.

truecharts/charts#9116

The ingressClass* now doesn't work to pass the certificate the way the video explains. This apparently was not intended to work this way in the first place and a breaking update was made after the breaking change update.

It would be great to have an amendment in the video or an update on how to restore functionality.

Wrong Title

There is a Wrong Title in the https://github.com/ChristianLempa/videos/tree/main/nginx-reverseproxy#readme

'Bad Gateway' on nextcloud, nginx proxy login

When I attempt the first login to nginx proxy manager, following the nextcloud video instructions, I receive a bad gateway error. I'm using the following docker-compose.yml:

version: "3"

volumes:
  nextcloud-data:
  nextcloud-db:
  npm-data:
  npm-ssl:
  npm-db:

networks:
  frontend:
    # add this if the network is already existing!
    # external: true
  backend:

secrets:
  mysql_root_password:
    file: ./mysql_root_password.txt
  mysql_password:
    file: ./mysql_password.txt

services:
  nextcloud-app:
    image: nextcloud
    restart: always
    volumes:
      - nextcloud-data:/var/www/html
    environment:
      - MYSQL_PASSWORD_FILE=/run/secrets/mysql_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=nextcloud-db
    networks:
      - frontend
      - backend
    secrets:
      - mysql_password

  nextcloud-db:
    image: mariadb
    restart: always
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    volumes:
      - nextcloud-db:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
    networks:
      - backend
    secrets:
      - mysql_root_password

  npm-app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - "80:80"
      - "81:81"
      - "443:443"
    environment:
      - DB_MYSQL_HOST=npm-db
      - DB_MYSQL_PORT=3306
      - DB_MYSQL_USER=npm
      - DB_MYSQL_PASSWORD_FILE=/run/secrets/mysql_password
      - DB_MYSQL_NAME=npm
    volumes:
      - npm-data:/data
      - npm-ssl:/etc/letsencrypt
    networks:
      - frontend
      - backend
    secrets:
      - mysql_password

  npm-db:
    image: jc21/mariadb-aria:latest
    restart: always
    environment:
      - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password
      - MYSQL_DATABASE=npm
      - MYSQL_USER=npm
    volumes:
      - npm-db:/var/lib/mysql
    networks:
      - backend
    secrets:
      - mysql_root_password

Invalid port

If you have this problem

services.nginx-mailcow.ports is invalid: Invalid port ":443:443", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]

Here how you can fix it:

1. In /opt/mailcow-dockerized you will find .env file.
2. Run nano .env.
3. Search for:

HTTP_PORT=80
HTTP_BIND=

HTTPS_PORT=443
HTTPS_BIND=

Change it to:

HTTP_PORT=80
HTTP_BIND=0.0.0.0

HTTPS_PORT=443
HTTPS_BIND=0.0.0.0

4. CTRL + O then CTRL + X.
5. Now Run docker-compose up -d.

Credited to eddytnk