Upgrade Keycloak Standalone with Postgres from 16.1.0 to 17.0.0 with custom port behind nginx reverse proxy

What a nightmare.

You’re using keycloak and are upgrading from Wildfly 16.1.0 to Quarkus 17.0.0.
You’re also listening on a non-standard port, that isn’t 8080, but 23232.
You’re using a reverse proxy like nginx for TLS
and Keycloak is connected via plain http with nginx.

Grab your standalone.xml found in /standalone/configuration/standalone.xml
and find your postgres jdbc connection string as well as postgresql username and password.

edit conf/keycloak.conf

With this everything should work as before.

You also have to upgrade your Java version to be at least v11. Keycloak 17 won’t run with v8.

Lost Ark: Can’t play on EU servers? 10027? Switch region to US East and play without queues

You’ve been trying to play Lost Ark on Central European servers and you’re getting 10027 error or high queues?
Why bother going through all that nerve wrecking stuff?
Just switch the server region to US East.
It’s the closest one to Europe and ping is between 90-110ms, absolutely playable fine.
Continue reading “Lost Ark: Can’t play on EU servers? 10027? Switch region to US East and play without queues”

Prophecy: If Russia doesn’t start a war USA will do a false flag operation to start one

The USA is known for false flag operations since at least 9/11. Letting planes crash into buildings by not preventing it despite better knowledge as well as blowing up their own buildings with controlled demolitions, thus justifying a war against Iraq and Afghanistan.
Continue reading “Prophecy: If Russia doesn’t start a war USA will do a false flag operation to start one”

centos 7 & mysql 5.7 gpg key error proper solution

If you’re running CentOS7 and using the MySQL 5.7 community rpm package you might’ve ran into this error response:

Seems like Oracle has changed their GPG key and it’s not uploaded to gpg servers yet, at least yum can’t find the new key.
So you have to manually replace your key.

Disabling gpgcheck is a very bad idea and should never be done, despite what some chinese blogger suggests for a solution. (https://www.cnblogs.com/minseo/p/15835416.html)
The proper solution is to take the key from the mysql5.7 gpg signature checking documentation page and replace the current contents of /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql with this key.

I will replicate the key here, but be sure to check mysql5.7 gpg signature checking documentation page for the current signature.

DO NOT DISABLE gpgcheck as suggested in the chinese blog.