Posts

Showing posts from February, 2022

minecraft

my directory location is /home/mysqli/server/  Failed to verify user name  online-mode=true change to false in server.properties sudo useradd -r -m -U -d /opt/mysqli -s /bin/bash mysqli iptables -I INPUT -p tcp --dport 25565 --syn -j ACCEPT /etc/systemd/system vi minecraft.service systemctl start minecraft.service systemctl status minecraft.service [Unit] Description=Minecraft Server After=network.target [Service] User=mysqli Nice=1 KillMode=none SuccessExitStatus=0 1 ProtectHome=true ProtectSystem=full PrivateDevices=true NoNewPrivileges=true WorkingDirectory=/opt/minecraft/server ExecStart=/usr/bin/java -Xmx4024M -Xms4024M -jar server.jar nogui ExecStop=/opt/minecraft/tools/mcrcon/mcrcon -H 127.0.0.1 -P 25575 -p bumkailash stop [Install] WantedBy=multi-user.target Setup Instructions 1. Install Java The first step is to make sure that we have Java installed. Minecraft requires Java 1.8 or higher, so we must verify the installed version using  java -version . [user@host ~]$ java -versi

color code

 bright yellow color code   #FFFF33

pdo required pdo extension missing

 install php mysql extesnion for the same php version php81-php-mysqlnd in easy apache php extesion

Admin Backup/Transfer not restoring reseller information

  cd /usr/local/directadmin/scripts ./set_permissions.sh da_files ./fix_da_user.sh [B]resellername[/B] reseller

Apache and X-Forwarded-For Header (XFF)

  It's easier to get Apache to log client IP addresses utilizing X-Forwarded-For Headers than it is using IIS. By default, the logs do not record source IP addresses for clients - but as of Apache version 2.4 you can use the ErrorLogFormat directive in the httpd.conf file as explained below. ->Did you want to learn about  XFF on IIS ? There’s been a lot of debate here in the office about how best to capture both your Loadbalancer’s IP and the Source IP of the user in your access_log in  Apache 2.4 . This is the tried and tested method we've come up with. How to log X-Forwarded For Headers using Apache 2.4 CentOS 7 When you start out, your httpd.conf will look something like this: LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common CustomLog "logs/access_log" combined Now the  %h  is already there to capture your header, which

How to install or enable mod_remoteip?

  I use cloudflare but need access to original remote IP address. Cloudflare no longer support mod_cloudflare for debian 9 and recommend mod_remoteip. I’ve tried the following instructions but with no joy. You only need to enable the mod_remoteip module in the  /opt/bitnami/apache2/conf/httpd.conf  file LoadModule remoteip_module modules/mod_remoteip.so Once uncommented, you can verify that the module will be loaded properly $ apachectl -M | grep remote remoteip_module (shared) before restarting Apache sudo /opt/bitnami/ctlscript.sh restart apache Mod_remoteip Bitnami stacks ship with the  mod_remoteip  module installed, but it is not enabled by default. To enable this module, follow these steps: Edit the main Apache configuration file at  /opt/bitnami/apache2/conf/httpd.conf  and add the line shown below: ... LoadModule remoteip_module modules/mod_remoteip.so Restart Apache and confirm that the module is active: sudo /opt/bitnami/ctlscript.sh restart apache sudo apachectl -M |

How to get X-Forwarded-For IP addresses in Apache Web Server

  How to get X-Forwarded-For IP addresses in Apache Web Server X-Forwarded-For, or XFF for short, is a special HTTP header field that is commonly used to identify the originating client IP address whether or not they are connecting to the server through an HTTP proxy or a load balancer. Such web hosting cases where the web server is behind a proxy or a load balancer are extremely common, and thus arises the necessity to be able to log the actual client’s IP address in your system instead of the proxy or load balancer IP. In order to be able to identify the client, you will need to configure your back end Apache HTTP Web Server to be able to use the XFF header and render the real customer IP in its log files. Otherwise, your Apache server will by default log only the receiving IP from the connecting proxy or load balancer. This guide will show you how you can configure your Apache web server to use the X-Forwarded-For header information so that you can avoid corrupt or incorrect logged