We're Back

[1-0-0-1-0-0-1]

So can you not view ANYTHING without signing in first?

 

That's just temporary, needed to deny access to guests while I repaired the database so all the spambots wouldn't keep trying to look at stuff. Will change that back in a bit.

[Principled Man]

Site is running a lot better then it was the other day (and for a while to be honest). Recently has been taking 5-10 seconds to load a page.

 

Yes, it had been lagging for a long while, but something happened on Feb. 26th that started a fast and drastic downturn in performance. The normal maintenance measures weren't fixing whatever this was, so we had to try different measures, which so far seem to have worked.

 

 

You NEVER press the RED Button!!

 

[1-0-0-1-0-0-1]

Site is running a lot better then it was the other day (and for a while to be honest). Recently has been taking 5-10 seconds to load a page.

 

Yes, it had been lagging for a long while, but something happened on Feb. 26th that started a fast and drastic downturn in performance. The normal maintenance measures weren't fixing whatever this was, so we had to try different measures, which so far seem to have worked.

 

 

You NEVER press the RED Button!!

 

 

Sometimes you do...

 

[invisible airwave]

Wow I had hernia surgery on Monday and missed all of this excitement!

 

TRF had hernia surgery yesterday!

 

I feel bad!

 

[Hatchetaxe&saw]

WHAT DOES THIS PLUG DO?

 

So....it WAS you!!!

 

 

Oh and, that box of donuts on the table in the green room was for the night crew. You know this.

 

I WAS HUNGRY, UNPLUGGING IS QUITE EXERTING.*

 

 

 

*that's what she said

[Bahamas]

Thank you for all the behind the scenes work to keep us all happy, much appreciated!

[Leanne]

So can you not view ANYTHING without signing in first?

 

That's just temporary, needed to deny access to guests while I repaired the database so all the spambots wouldn't keep trying to look at stuff. Will change that back in a bit.

 

Thank you for your hard work!

[invisible airwave]

WHAT DOES THIS PLUG DO?

 

So....it WAS you!!!

 

 

Oh and, that box of donuts on the table in the green room was for the night crew. You know this.

 

I WAS HUNGRY, UNPLUGGING IS QUITE EXERTING.*

 

 

 

*that's what she said

 

And Leon's getting larger!

Edited March 5, 2022 by invisible airwave

[grep]

Thanks for bringing it back! I know these boards are ..difficult.. sometimes.

 

Nice work.

[Babycat]

:yay: :cheers: :yay: Woohoo! :yay: :cheers: :yay:

[Babycat]

Oh my God, I'm a Ghost Rider! :o How did that happen?! :D

[blueschica]

Oh my God, I'm a Ghost Rider! :o How did that happen?! :D

 

Congratulations! And I can see and read it all from my phone! This is great! Such a cool icon for you!

[Babycat]

Oh my God, I'm a Ghost Rider! :o How did that happen?! :D

 

Congratulations! And I can see and read it all from my phone! This is great! Such a cool icon for you!

 

:D

[Rhyta]

Thank you! :cheers: :sundog:

Been gone a few days and missed all the fun :LOLsign: No 404's tonight...great work :ebert:

[Laurabw]

I'm still having issues even getting the site to load at all on Chrome and Edge both.

[1-0-0-1-0-0-1]

I'm still having issues even getting the site to load at all on Chrome and Edge both.

 

Are you still getting 404s, or are some forums like RS taking some time to open up? Is anyone else having similar issues still?

[Laurabw]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

[Laurabw]

Actually take it back again. I just tried navigating around the site and ran into the same issue. Not a 404 just spinning and spinning. I also notice it takes at least a minute to logout and off and I have to try it a few times Edited March 9, 2022 by Laurabw

[1-0-0-1-0-0-1]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

[Fridge]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

 

Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in.

[1-0-0-1-0-0-1]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

 

Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in.

 

I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing.

[JARG]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

 

Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in.

 

I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing.

 

Our pages are are asp.net, but here's a redirect I wrote to handle a related issue where we want to load our https page even if users came to it from an http link:

 

 

string current_url = HttpContext.Current.Request.Url.AbsoluteUri;

if(current_url.IndexOf("https://") == -1)

{

current_url = current_url.Replace("http://", "https://");

Response.Redirect(current_url);

}

 

 

It may be possible to do something similar here.

[1-0-0-1-0-0-1]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

 

Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in.

 

I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing.

 

Our pages are are asp.net, but here's a redirect I wrote to handle a related issue where we want to load our https page even if users came to it from an http link:

 

 

 

string current_url = HttpContext.Current.Request.Url.AbsoluteUri;

if(current_url.IndexOf("https://") == -1)

{

current_url = current_url.Replace("http://", "https://");

Response.Redirect(current_url);

}

 

 

It may be possible to do something similar here.

 

Yeah, we're in the opposite boat right now -- search engine links looking for an https TRF and not finding us because we're still http. Once we're https compliant, the search engine links should connect right up. We'll find out soon enough.

 

That redirect you wrote could be something to use in the short term, though. Can you simply flip-flop the http and https in that Replace command?

[JARG]

I was getting 404s. Eventually it opened on Edge. But on Chrome, it spins from the search engine. Oh, but when I put the actual address in the search bar, then it comes up right away. Hm. OK then I guess it's ok?

 

That's why we're finally getting this site https compliant in a couple of weeks. Right now the address for this site is http://www.therushforum.com, but the search engines like Google and DuckDuckGo have us listed as https://www.therushforum.com. So when you click their link, you get nothing. I had no idea they had us listed that way until recently.

 

Ah, that explains that little issue...had me scratching my head...had to an alternative route to log in.

 

I can't believe how long that problem has existed. It's not something I ever thought to check for, even knowing we were still in need of an SSL certificate -- "Does our link in a search result actually work?" Who knows how many people were looking for a Rush forum to join, found us on Google, clicked the link and got nothing, then just walked away. It's embarrassing.

 

Our pages are are asp.net, but here's a redirect I wrote to handle a related issue where we want to load our https page even if users came to it from an http link:

 

 

 

string current_url = HttpContext.Current.Request.Url.AbsoluteUri;

if(current_url.IndexOf("https://") == -1)

{

current_url = current_url.Replace("http://", "https://");

Response.Redirect(current_url);

}

 

 

It may be possible to do something similar here.

 

Yeah, we're in the opposite boat right now -- search engine links looking for an https TRF and not finding us because we're still http. Once we're https compliant, the search engine links should connect right up. We'll find out soon enough.

 

That redirect you wrote could be something to use in the short term, though. Can you simply flip-flop the http and https in that Replace command?

 

That, and you change the check from == -1 to > -1, so this:

 

if(current_url.IndexOf("https://") > -1)

{

current_url = current_url.Replace("https://", "http://");

Response.Redirect(current_url);

}

 

The previous check says "if the page URL doesn't contain 'https://' then do the swap. This one says "if the page URL does contain 'https://' then do the swap, only this time the swap is flip-flopped.

[Laurabw]

So I say this, not to complain but just purely informational. I'm still having trouble on Chrome navigating between pages and also logging out, that's when I get the 404