Site update news ...

[xfadmin]

We will be issuing our monthly server reboot on Saturday, June 10 at approximately 6:30 AM EDT.

This reboot will implement approximately 120 security patches, software and firmware updates accumulated and uploaded over the past month.

The forum will be down for approximately 90 seconds while the server reboots and brings the forum, database and Java virtual machine back on-line.

 

[xfadmin]

We will be issuing our monthly server reboot on Saturday, June 10 at approximately 6:30 AM EDT.

This reboot will implement approximately 120 security patches, software and firmware updates accumulated and uploaded over the past month.

The forum will be down for approximately 90 seconds while the server reboots and brings the forum, database and Java virtual machine back on-line.

Reminder to all that the system reboot will be happening tomorrow (Saturday) morning.

 

[xfadmin]

We will be bringing the forum down for approximately 30 minutes on SATURDAY, June 17 at 7:00 AM EDT.

This will be for a full system snapshot backup, and then a significant update to the Wiki software. The Wiki software has not been updated since November, 2022.

 

[xfadmin]

The site administrator will be unavailable for any technical issues/problems from Monday, July 10 through Thursday, July 13 due to being in the hospital for scheduled surgery.

Please refer to @gsxr and/or @Glen for any administrative issues during this time.

Thanks
@xfadmin

 

[xfadmin]

We will be issuing our monthly server reboot on Sunday, July 20 at approximately 7:00 AM EDT.

This reboot will implement approximately 50 security patches, software and firmware updates accumulated and uploaded over the past month.

The forum will be down for approximately 90 seconds while the server reboots and brings the forum, database and Java virtual machine back on-line.

 

[xfadmin]

We will be issuing our monthly server reboot on Wednesday, August 30 at approximately 7:30 AM EDT.

The reboot will implement many of the security, firmware and software patches that have accumulated over the course of August.

Forum will be down for approximately 1.5 minutes while the system comes back up.

 

[xfadmin]

The site will be down on THURSDAY, January 11 at 6:00 PM EST, for approximately 15-20 minutes for a full system backup, and then the installation of updated modules that power the search and look-ahead search capability.

 

[gerryvz]

A note for all members here that the 126board is now — again — live and up & running.

No data was lost and the forum should be picked up where it left off last year.

This is a note for the attention of @nocfn @liviu165 @jhodg5ck @AMG5PT4 @GRAEME JOHNSON @Trae @bclifton @7delta @luckymike and many others who frequented that forum.

Please let me know if you have any issues accessing it.

It has been an extremely difficult time to get that forum up and running again, what with personal stuff going on and also the recent resumption of the M104/G320 cylinder head refurbishment.

This forum is next, with a significant back-end technology update and refurbishment already underway and slated for completion in the next few weeks.

A lot of things behind the scenes on this forum will be changed and modernized since this forum’s technology base was established in February 2019. That was over six years ago — which in software terms may aswell have been 20 years ago.

So while this forum is on an extremely stable and mature tech platform, it needs a bit of modernization.

We will also be skipping XenForo 2.3 (we are currently on XF 2.2.17) and we will be jumping directly to XenForo 2.4 when it becomes generally available. It is in late Beta testing now.

Cheers
Gerry

 

[gsxr]

I'm currently getting a "Page could not be loaded" error, but I assume that's temporary... works fine on my work PC via VPN.

 

[gerryvz]

I am also getting same -- although it is loading on some networks. The site is not loading on my home network, but if I get on my work VPN, or switch my phone to mobular only (AT&T), the site loads just fine. I also was able to access the site about an hour ago via cellular network on my phone when I was at the hospital with my wife.

Looks like some additional work needs to be done to diagnose this issue.

 

[liviu165]

This is what I get:

 

[gerryvz]

It is showing up on "is this site down?" web sites as being up. It's not accessible from some connections.



We are looking into why this is. Please rest assured that the site IS working as designed, but there appears to be a mis-configuration in the server / DNS / SSL certificate. We are working on getting this resolved.

To access the site, please try alternate networks, or a cell phone, etc.

 

[gerryvz]

This is what I get:

Should be fixed now.

 

[liviu165]

I am still getting the same thing on the laptop.

However, I can access on the cell, which is a step forward, considering that in the past I was not able to do that. I can also access on the laptop, if I connect it to a hot spot generated by the cell.

 

[gerryvz]

I am still getting the same thing on the laptop.

However, I can access on the cell, which is a step forward, considering that in the past I was not able to do that. I can also access on the laptop, if I connect it to a hot spot generated by the cell.

Hi Roy,

Please see other thread on this. My testing as of about 9PM ET on Tuesday night, and ongoing this morning, is showing that all issues are resolved.

I have accessed the 126board.com site on three different networks:

1. AT&T cellular network
2. Verizon FIOS home network (via wireless router, unplugged & rebooted yesterday evening)
3. My employers VPN

Accessed via FOUR different computers:

1. My main home Macintosh computer (home wireless network and hotspot network with AT&T iPhone)
2. My work laptop computer (home wireless network and employer's VPN network)
3. My iPad at home (home wireless network)
4. My iPhone (home wireless network and AT&T network)

Using NINE different browsers:

1. Safari on home Macintosh (home wireless network and hotspot network with AT&T phone)
2. Chrome on home Macintosh (home wireless network and hotspot network with AT&T phone)
3. Firefox on home Macintosh (home wireless network and hotspot network with AT&T phone)
4. Edge on home Macintosh (home wireless network and hotspot network with AT&T phone)
5. Chrome on work laptop computer (home wireless network and employer's VPN network)
6. Safari on work laptop computer (home wireless network and employer's VPN network)
7. Chrome on iPad (home wireless network)
8. Safari on iPad (home wireless network)
9. Safari on iPhone (home wireless network and AT&T network)

Access with all of these browsers, computers and networks in all combinations is 100% successful as of last night.

Recommendations for resolution:

• Quit your browser, and then restart the browser application
• IF USING Chrome browser, enter the following into the URL line: chrome://net-internals/#dns Click once on the "Clear Host Cache" button. Then Quit Chrome and restart the application
• Unplug your home wireless router, wait 60 seconds, then plug it back in and let it fully reboot (3-5 minutes)

 

[gerryvz]

I'm currently getting a "Page could not be loaded" error, but I assume that's temporary... works fine on my work PC via VPN.

Please retry and advise, thanks @gsxr.

 

[gsxr]

Please retry and advise, thanks @gsxr.

I'm traveling today - will check tomorrow when I'm back home.