1022
port in Security List / Ingress Rules
for your VCN
The tmpfs
partition is limited to 700m
for x86_64
(free tier) compatibility.
#!/bin/sh | |
# Remove the performance overlay, it meddles with some tasks | |
unset LD_PRELOAD | |
## Shadow kwin_wayland_wrapper so that we can pass args to kwin wrapper | |
## whilst being launched by plasma-session | |
mkdir $XDG_RUNTIME_DIR/nested_plasma -p | |
cat <<EOF > $XDG_RUNTIME_DIR/nested_plasma/kwin_wayland_wrapper | |
#!/bin/sh |
1022
port in Security List / Ingress Rules
for your VCN
The tmpfs
partition is limited to 700m
for x86_64
(free tier) compatibility.
❯ multipass launch \
-m 8G \
-c 4 \
-d 30G \
--name dockrr \
focal
Launched: dockrr
When you are unable to login to the unifi controller or forgot admin password, you can restore access using SSH and manipulating mongodb directly.
Do not uninstall unifi controller - most of the data is not stored in mongodb. In case you thought a mongodb backup would be sufficient, you may have fucked up already, just like me. However I managed to write this "tutorial" for anyone to not run into the same trap.
Apparently this guide no longer works with recent unifi controller versions (starting nov/dec 2022). Since I no longer use unifi hardware in my home system, I can not update the guide myself. In case you've gotten here to recover your data, you're likely doomed. But giving it a try won't hurt anyway, therefore: good luck.
# Jos käytät mod_rewriteä, älä rewriteä acme-challenge kansiota | |
RewriteRule ^\.well-known\/acme-challenge\/ - [L] |
Enable systemd-networkd debugging | |
mkdir -p /etc/systemd/system/systemd-networkd.service.d/ | |
Create Drop-In /etc/systemd/system/systemd-networkd.service.d/10-debug.conf with following content: | |
[Service] | |
Environment=SYSTEMD_LOG_LEVEL=debug | |
And restart systemd-networkd service: | |
systemctl daemon-reload |
Vagrant.configure(2) do |config| | |
config.vm.box = "ubuntu/trusty64" | |
config.vm.provider "virtualbox" do |vb| | |
vb.memory = "1024" | |
end | |
config.vm.provision "shell", inline: <<-SHELL |
This gist was essentially created out of my own rant about Netflix being hostile to IPv6 tunnel services since June 2016. You are welcome to read my opinion on the matter, this is the more technical side to the issue and how to combat it within your own network.
Since I wrote this, various GitHub users have contributed their thoughts and ideas which has been incorporated into this gist. Thank you to everyone who have contributed their own methods and implementations.
Netflix now treats IPv6 tunnel brokers (such as Hurricane Electric) as proxy servers. A while ago it became apparent to users and Netflix that somewhat by accident, IPv6 tunnel users were being served content outside of their geolocation because of the way Netflix was identifyi