Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Error 502 Continues to Cause Issues - Please Be Patient

Featured Replies

A websitedown.org test some minutes ago produced this:

img%5D

... and that's why I used a Singapore node; in case some of you can't see the imgur image:

Mixed signals for msfn.org: Reachable in 2of 8 signals, with regional or policy differences elsewhere.

US East (IAD): Server error 502 Bad Getway
US West (SFO): Server error 502 Bad Getway
Europe (CDG): Server error 502 Bad Getway
Europe Central (FRA): Server error 502 Bad Getway
South America (Sao Paolo): Timed Out
Asia East (Tokyo): Server error 502 Bad Getway
Asia Pasific (SIN): Reachable 200 OK
Ocania (Sydney): Reachable 200 OK

In the hope it helps 😸 ...


... And now, ALL is GREEN:

img%5D

... and I, after so many hours, can again connect through my own Greek IP; I'm losing my sanity, it seems...

  • xper changed the title to Error 502 Continues to Cause Issues - Please Be Patient

@xper Is this all just server overload?

ie, the gateway errors have NOTHING to do with the visitor's IP Address, but all about the CPU Percentage at the time of the visitor's attempted visit?

4 minutes ago, NotHereToPlayGames said:

@xper Is this all just server overload?

ie, the gateway errors have NOTHING to do with the visitor's IP Address, but all about the CPU Percentage at the time of the visitor's attempted visit?

It is not entirely correct.

It's something among these. It's not a lack of memory.

The Backend Server is Down: Apache or PHP-FPM crashed or stopped running because of a configuration error or lack of memory.

Configuration Syntax Error: A leftover Cloudflare rule or file was deleted, but another configuration file is still looking for it, causing a processing failure.

A Connection Timeout: Invision Community 5 application took longer than 60 seconds to process a request (like rebuilding its Redis cache), so Nginx gave up and dropped the bridge.

Firewall Blocks: CSF firewall is misinterpreting the local communication between Nginx (Port 80) and Apache (Port 8181) as an attack and is blocking it.

cpu.png

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.