Clubarnage forum was just unavailable for a little while, I think it was caused by a problem I noticed last week - which means the webserver itself cannot do DNS lookups (blocked by firewall).
I will get this issue sorted asap. Sorry for the outage.

/Djet

Quote from: DJet on February 05, 2026, 03:29:00 PMbut there are other issues with the server now running with the active IP address...
Haven't found the reason yet, but I am working on it. 

That problem was found, and caused by an old syslog config that no longer works. It meant syslog didn't run on the server (in fact it segfaulted), which makes it rather hard to find, as there is no logging to tell you :-)

/L

Quote from: Kev_mk3 on February 05, 2026, 05:21:30 PMShock to the eyes when I logged in thought you'd broken something at first!

LOL :-)
Yes its bright and shiny - and running the very latest forum software ! :-)

In my endeavours I even obtained access to a few thousand old attachments, that had gotten lost in previous (ancient) upgrades.  I doubt anybnody notices, but I like it.

Avatars may have been lost though - they now live in a different dir, but were not always listed in a way that told me it was an avatar. But folks can upload new ones at will.


/L

but there are other issues with the server now running with the active IP address...
Haven't found the reason yet, but I am working on it. 

YAY! - servers are swapped and new server/forum is in place and hopefully working for the foreseeable future !

The only niggle was that the old server refused to go down for a reboot, but that was sorted.

I will let you all get used to ne new look and features - and if you spot things please just let me know.

/Lennart "Djet"

The process of sync'ing the current databases down to my VM, tidying certain database entries, and upgrading that, and uploading a backup of the converted database to the new server can seemingly be done in about half an hour.

Then I need the IP change, which probably is safest done by reconfigure and reboot - which for these enterprise servers takes a fair bit of time - but I still think the entire task can be held within an hour.

I am in Denmark right now, and only a couple of hours away from the datacentre where the server is located, so if I do this during the daytime, and possibly have some of my old colleagues available as first resort, then a train and a bus as last resort, should something go wrong.

I guess this all reveals my 20 year experience running large datacentres with absolute demands that any "system session" is planned, announced, executed and able to be rolled back within the specified time :-)

Heh - I remember exactly where I was, and which chair I was sitting on at the Apollo 11 landing  - mind you, I was only 7 at the time, but its deeply printed in my memory. :-)

I missed my own deadline of doing this server swap in January, but with good reason, as I am traveling to Denmark tomorrow anyway for a few weeks - which puts me closer to the datacentre it is located at - should it all go titsup.  I have management access to the newer server, but not to the old, so IP change can go wrong.
I have human contacts in the datacentre too, but being a few hours away from the datacentre seem like an even better option.   :-)

So one of the days in the following week or two I'll put the forum in "maintenance mode" and get on with it.

Once back up, it should also allow HTTPS, which most browsers insist on these days - but we may have to live with some "scary" messages about a "self signed certificate" - but I have a plan to fix that later,.

/L

OK,
I have scripted the remaining bits, so I can:

1) Set the current forums to "maintenance mode" - which will prevent updates while the upgrade happens.
2) download the newest data from the active forums (ClubArnage.com/forum  and MatraSport.dk/forum))
3) do a little housekeeping with database contents and directories, ownership etc
4) perform the regular 2.0.19->2.1.6 upgrade on both forums
5) patch the one Source file that has a known bug (Class-Punycode.php)
6) dump the database opf both forums, and restore it on the new server's 2.1.6 installation.

and I completed that in less than 20 minutes.

So we are very close to me actually making this jump ... :-)

/Lennart

More updates.
I now have the new(er) server running with the newest OS and the newest forum software, and I have a semi automatic way to update the newer server with the latest posts and messages from the running forum.

So all I need it to take a very deep breath, and swap the IP addresses and sort out whatever falls on the floor. :-)

However at this time of year, time is limited, so I think I will aim at early January for that switch. Fingers crossed :-)

/Lennart aka DJet

progress is still happening.
I am making this update simply to see if my virtual environment picks it up.

also, - I have updated the phrasing of that annoying database error you sometimes get at login (which just require you to reload your browser tab to continue) - so it now actually says so:

Before:
   The database value you're trying to insert does not exist: p_member_ip

now at least :
   The database value you're trying to insert does not exist: p_member_ip - please just reload your browser tab to continue

This will go away when we get to the newest forum version. I have had a look, but it seems too difficult to fix the error in this version, and also somewhat waste of time as we will soon get on the new version.

ok, by cross-referencing the Apache log, with the varnish (proxy/cache) enormous log, I have updated the IP address of the user registrations that got listed as 127.0.0.1 (until I patched the SMF files).

That means now we can at least see where they came from in admin/members.

There are a number og Russian and Middle-East ones - to save you the lookup, I include the table here (you need a wide screen):

id    username            email                           IP(wrong)  Date-of-registration       real-IP            whois-info
4259  Claude-roand        claude.francoise@ggmail.website 127.0.0.1  Oct 13, 2025, 02:08:19 pm  95.221.198.192     Net By Net Holding LLC, Moscow, Russia
4258  Keithtaply          66@woldex.online                127.0.0.1  Oct 13, 2025, 08:46:05 am  91.84.115.213      SERVERS TECH FZCO, Ifza Business Park, Dubai
4257  Jaimenuddy          e1qrq1q1wr2qq1d@gmail.com       127.0.0.1  Oct 13, 2025, 07:09:11 am  31.130.137.252     LLC "AVANTA TELECOM", Russia
4256  Arthuroxift         salesx19@iartun.com             127.0.0.1  Oct 13, 2025, 02:47:55 am  185.247.184.90     GLOBAL INTERNET SOLUTIONS LLC, Russia
4255  Azerea              a@xelo.pro                      127.0.0.1  Oct 12, 2025, 10:38:37 pm  88.97.246.218      YouFibre, London, UK
4254  AnthonysBup         olga.grigor070797@gmail.com     127.0.0.1  Oct 12, 2025, 04:17:57 pm  192.109.138.145    RIPE, NL ...
4253  Romatriag           gasiogarit@gmail.com            127.0.0.1  Oct 12, 2025, 01:29:46 pm  109.107.186.56     SERVERS TECH FZCO, Ifza Business Park, Dubai
4252  PhillipCic          adv25@aolimo.com                127.0.0.1  Oct 12, 2025, 09:09:00 am  91.228.155.80      Fornex Hosting, Estepona, Spain
4251  123bzIply           123bv9@123bv1.it.com            127.0.0.1  Oct 12, 2025, 04:02:56 am  45.117.164.56      IRT-VNNIC-AP, Ha Noi, VietNam
4250  123bJoync           123bv9@123bv2.it.com            127.0.0.1  Oct 12, 2025, 01:44:52 am  103.151.53.189     IRT-VNNIC-AP, Ha Noi, VietNam
4249  123bEnelp           123bv7@123bv1.it.com            127.0.0.1  Oct 12, 2025, 01:23:07 am  103.188.242.81     IRT-VNNIC-AP, Ha Noi, VietNam
4248  BrianBut            mrtommyk@gmail.com              127.0.0.1  Oct 12, 2025, 12:14:22 am  5.143.41.95        PJSC Rostelecom, Russia
4247  TimothyRix          xrujujikis@anonmails.de         127.0.0.1  Oct 11, 2025, 12:05:49 pm  5.196.78.175       OVH SAS, Roubaix, France
4246  Williamanise        nikita356314@gmail.com          127.0.0.1  Oct 11, 2025, 08:39:01 am  46.8.221.114       Contel OOO, Bazhova, Moscow, 129128, Russia
4245  CharlesExone        ha.luongkim95@gmail.com         127.0.0.1  Oct 11, 2025, 08:00:41 am  192.73.244.36      NetActuate, Inc, Raleigh, NC
4244  muzxyz              dvfkpqulq@zvezdaforum.ru        127.0.0.1  Oct 10, 2025, 09:28:41 pm  188.130.211.102    Biterika Group LLC, Russia, Moscow
4243  ShopforMib          ejwfmfcc@cetakexpress.com       127.0.0.1  Oct 10, 2025, 07:20:53 pm  150.136.58.182     Oracle Corporation, Austin, TX
4242  xrbyjwbbm           bms@brandshield.com             127.0.0.1  Oct 10, 2025, 05:05:02 pm  194.62.55.202      SiberDC, Kavacik Mah. Fatih Sultan Mehmet Cad, TL
4241  evichepic           zarahsmallive64235o@ctive.org   127.0.0.1  Oct 10, 2025, 04:24:18 pm  158.173.3.3        RIPE, NL ...
4240  Louisreant          okna.master.vitebsk@gmail.com   127.0.0.1  Oct 10, 2025, 10:45:00 am  45.88.106.84       RIPE, NL ...
4239  Holographicomi      irishpolevaultmonkey@gmail.com  127.0.0.1  Oct 10, 2025, 09:47:36 am  98.188.47.132      Cox Comms, Atlanta, US
4238  Passneinc           gugloff.444@gmail.com           127.0.0.1  Oct 10, 2025, 02:18:13 am  146.103.106.124    RIPE, NL ...
4237  Independentvsa      michael.flynn@davispolk.com     127.0.0.1  Oct 10, 2025, 02:15:02 am  72.214.108.67      Cox Comms, Atlanta, US
4236  123bNig             123bv4@123bv2.it.com            127.0.0.1  Oct 10, 2025, 01:33:35 am  45.117.164.30      ODS Joint Stock Co, Ho Chi Minh city, Vietnam
4235  Artkameraru_Kib     building.sal.e.sru@gmail.com    127.0.0.1  Oct 09, 2025, 03:05:54 pm  95.27.42.178       CORBINA TELECOM Network Operations, Russia
4234  Josephdiste         adv@iartun.com                  127.0.0.1  Oct 09, 2025, 11:26:14 am  5.253.31.94        GEOHOSTING-NOC, Buharest, Romania
4233  NAERTREGE1187604NEWETREWT zaojhaxi@tubermail.com    127.0.0.1  Oct 09, 2025, 07:42:52 am  165.231.182.14     N I Team, Johannesburg, South Africa
4232  krakenruss          yourmnui8ail@gmail.com          127.0.0.1  Oct 09, 2025, 07:42:45 am  46.28.234.124      EUROHOSTER Ltd, 8000, Burgas, BULGARIA
4231  Awinroadads         wirople@igredan.fun             127.0.0.1  Oct 08, 2025, 11:10:11 pm  37.139.53.214      Kupriyanov Pavel Nikolaevich, Russia
4230  Normandjak          yourmail344@gmail.com           127.0.0.1  Oct 08, 2025, 05:45:18 pm  128.90.145.4       Unus Inc, Austin, TX, 78703, US
4229  Alfredpar           dser5857@gmail.com              127.0.0.1  Oct 08, 2025, 04:12:02 pm  192.73.244.36      NetActuate Inc, NC, 27605, US
4228  RichardVep          work777top@gmail.com            127.0.0.1  Oct 08, 2025, 02:06:37 pm  135.181.79.90      RIPE Network Coordination Centre (RIPE)
4227  123blouBy           123bv1@123bv2.it.com            127.0.0.1  Oct 08, 2025, 01:38:24 pm  103.188.242.20     BAO LONG MANAGEMENT CONSULTANT, Ha Noi, VietNam
4226  AlexanderNus        lev26971@gmail.com              127.0.0.1  Oct 08, 2025, 12:58:34 pm  212.192.55.206     193091 St.Petersburg Russia

My gut feeling is that most of these can be deleted - as they all occurred in a flush, just around the upgrade time, but I will let the moderators have a look.

/Lennart

Quote from: DJet on October 16, 2025, 06:17:45 PM
Lets see if new registrations gets logged with a real IP rather than 127.0.0.1

YEP,  new registrations gets logged with their correct IP now (I registered a user named "IP test" - checked the IP was logged, then I approved it, and deleted it)

Yay - I modified Sources/Load.php to force the code to use HTTP_X_FORWARDED_FOR rather than REMOTE_ADDR, which seems to have fixed the logged IP address on posts at least.

For reference here is a diff:
# diff  Sources/Load.php_ORG  Sources/Load.php
770c770
<             updateMemberData($id_member, array('id_msg_last_visit' => (int) $modSettings['maxMsgID'], 'last_login' => time(), 'member_ip' => $_SERVER['REMOTE_ADDR'], 'member_ip2' => $_SERVER['BAN_CHECK_IP']));
---
>             updateMemberData($id_member, array('id_msg_last_visit' => (int) $modSettings['maxMsgID'], 'last_login' => time(), 'member_ip' => $_SERVER['HTTP_X_FORWARDED_FOR'], 'member_ip2' => $_SERVER['BAN_CHECK_IP']));
894c894
<       'ip' => $_SERVER['REMOTE_ADDR'],
---
>       'ip' => $_SERVER['HTTP_X_FORWARDED_FOR'],
4058c4058


There is still a QueryString.php file which has many places I could do the same, but it doesn't seem to be required for what we need.

Lets see if new registrations gets logged with a real IP rather than 127.0.0.1

IP test