• Welcome to Simple Machines Community Forum. Please login or sign up.
November 27, 2021, 04:04:17 AM

News:

Wondering if this will always be free?  See why free is better.


Help Request : Redirection Error?

Started by TalonDOD, November 22, 2021, 01:47:12 PM

Previous topic - Next topic

TalonDOD

Hello, I have been using SMF since around 2009-10 and have never had any issues before, but this past week our forum would not let anyone log in or out (as well as some minor text alterations to past posts)

When you input your username/password and click to sign in, you are taken to a white page that never goes anywhere.  Upon further inspection the web address reads "http://espnsportssims.net/index.php?PHPSESSID=i8589fjqnb73pvdfltksaccia4&action=login2 [nofollow]"  When you delete the 2 from "login2" it takes you back to the main site and you appear to be logged in and can navigate the boards.

Then if you go to post, the address again directs to a white page with a =post2 ending the web address, and if you remove the 2 it reloads the post-reply page with this error message across the top of the screen:

"
Warning: fopen(/home/content/74/11180074/html/cache/data_5267681d750cb0336733d926032df22b-SMF-modSettings.php): failed to open stream: No such file or directory in /home/content/74/11180074/html/Sources/Load.php on line 2873

Warning: fclose() expects parameter 1 to be resource, boolean given in /home/content/74/11180074/html/Sources/Load.php on line 2877"

but the post does actually go through. 

All that being said, My only tech skills come from reading posts here and watching/reading guides to install and/or upgrade when needed, so when I went to my host for help they said:

"For the coding related issue you would need to check with your developer but seems like .ht access file or the index file is corrupted.

Yes it's just a redirection error sot he culprit here would be redirection files such as ht access - config.php - index.php-html
function.php"


I would be greatly appreciative if anyone could give me an idea or walkthrough of what I should do to resolve this issue, and if this issues is in a prior thread, if you could just direct me to that to save you the time of having to re-explain, I would be just as appreciative.

Thank you in advance for any help you may be able to provide, and if I need to provide any other information to help explain my issues just let me know what you need and I will try to provide it.



SMF version - 2.0.18
PHP Version 5.6

http://espnsportssims.net/phpinfo.php [nofollow]

http://espnsportssims.net/index.php [nofollow]



Thanks again,

Talon

Kindred

clear your smf cache (delete all the data* files in the cache directory)
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.<br /><br />"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

TalonDOD

Quote from: Kindred on November 22, 2021, 05:22:25 PMclear your smf cache (delete all the data* files in the cache directory)

Thank you for your quick response!

I went into my file manager on godaddy and went to the cache folder and cleared it out, then cleared my cache on my browser too just to be safe and am still receiving the same problem.

Is there another cache I should be looking for in my files?


Steve

How about Admin -> Maintenance -> Routine -> Empty the file cache ?

Don't know if that will help.
Please do not PM me for support.

TalonDOD

Quote from: Steve on November 23, 2021, 07:27:02 AMHow about Admin -> Maintenance -> Routine -> Empty the file cache ?

Don't know if that will help.

I followed that path and thought it was successful, but posting/logging in still creates the same errors.

For people who didn't clear their cache/cookies in their internet browsers to log out of their accounts when the issue first began, the message they receive when trying to post is: 

"The following error or errors occurred while posting this message:
Your session timed out while posting. Please try to re-submit your message."

Kindred

you have DIFFERENT errors.

1- to fix the session error. Change the cookie name. This will FORCE everyone to log in new and establish a new session. This should fix things for users who won't/can't/don't clear their browser cache

2- You had an error with the cache file being corrupt.   You deleted the cache files (all files starting with data in the cache directory).   Has the corrupted cache file error re-occured since doing that?

fix both those problems first. Those are easy to fix.

3- you have a login problem that causes a white screen of death (a white screen with no text at all)
THIS one is more complicated --   and you being on GoDaddy means that it's going to be even more difficult than it needs to be (note: GoDaddy sucks, plain and simple)

However.... to start with.  A WSOD is a SERVER SIDE error.
if the system is even half-way configured correctly, the WSOD will result in an entry in the server error log that will indicate WHAT is causing the error.        We can't debug too much more without that information.
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.<br /><br />"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

TalonDOD

Quote from: Kindred on November 23, 2021, 11:44:40 AMyou have DIFFERENT errors.

1- to fix the session error. Change the cookie name. This will FORCE everyone to log in new and establish a new session. This should fix things for users who won't/can't/don't clear their browser cache

2- You had an error with the cache file being corrupt.   You deleted the cache files (all files starting with data in the cache directory).   Has the corrupted cache file error re-occured since doing that?

fix both those problems first. Those are easy to fix.

3- you have a login problem that causes a white screen of death (a white screen with no text at all)
THIS one is more complicated --   and you being on GoDaddy means that it's going to be even more difficult than it needs to be (note: GoDaddy sucks, plain and simple)

However.... to start with.  A WSOD is a SERVER SIDE error.
if the system is even half-way configured correctly, the WSOD will result in an entry in the server error log that will indicate WHAT is causing the error.        We can't debug too much more without that information.


1 - I just changed the cookie name.

2 - I don't think the corrupted cache file error is re-occurring but I honestly am not sure how/where to see that.

3. I went into my file manager to the error logs folder after trying another WSOD and the folder is completely empty.

On the forum error log, this is what I have.

Apply Filter: Only show the error messages of this URLhttp://espnsportssims.net/index.php?action=admin;area=logs;sa=errorlog;desc;c315f09d5b=6124b0f4701772f0212ea8b2bb45d2bbApply Filter: Only show the errors with the same message2: Cannot modify header information - headers already sent by (output started at /home/content/74/11180074/html/index.php:2)Apply Filter: Only show the errors from this fileFile: /home/content/74/11180074/html/Sources/Load.php
Line: 2533

Kindred

no, the WSOD will not reflect in the SMF error log, because php itself is crashing.

You need to get the server error log. It's usually a file called errorlog. or error.log.
If, for some bizarre reason, GoDaddy is NOT recording server errors, then you need to have them turn it on.


That error in the SMF error log is something else entirely.
Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.<br /><br />"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

TalonDOD

Quote from: Kindred on November 23, 2021, 03:08:03 PMno, the WSOD will not reflect in the SMF error log, because php itself is crashing.

You need to get the server error log. It's usually a file called errorlog. or error.log.
If, for some bizarre reason, GoDaddy is NOT recording server errors, then you need to have them turn it on.


That error in the SMF error log is something else entirely.


I went into my file manager and pulled up the error log folder and of course, it was empty.

I'm on tech support chat with Godaddy right now trying to get them to get it logged and resolved.

Once I have something from them I'll share it here.  Thank you guys for all your help so far!

TalonDOD

I hate Godaddy.. here is what I got from them today.

"Our team said that you're using a third party application on your site. Website error logs files are set up by the application you used to built the site, it doesn't come with the hosting especially if it is on shared environment. If you didn't use any application, you need to review this with your web developer to create a script that will show website error logs. You can share the above article to your developer. Please clear cache and cookies of the browsers."

https://za.godaddy.com/help/setup-php-error-logging-26423 [nofollow]

This is the link she sent me, but their hosting page has been giving me a 400 bad request error for weeks despite all my cache clearing.


Steve

This is what that link says:

QuoteSetup PHP error logging

When troubleshooting PHP errors, you will want to review your PHP logs. If you don't have PHP logs to review, use the following process to set up logging:

Note: For WordPress and Managed WordPress error logging please see Enable debugging to display errors in WordPress.

    You should always backup your site before making any changes to your site.

    Locate your PHP initialization file.

    Edit the file. (cPanel / Plesk / VPS)

    Place the following line in your initialization file:

    error_log = /path/to/your/webroot/php_error.log

        error_log is the PHP function that will tell the web server to output your logs to a new file.

        /path/to/your/webroot/php_error.log is the path to your new log.

            Make sure to replace /path/to/your/webroot with the actual path your hosting account uses.

            What is my absolute path? (cPanel / Plesk).

    Create the a file named php_error.log in the in the webroot of your hosting.

    Restart your PHP processes.(cPanel / Plesk).

Next Steps:

    Review your php_error.log for error details. (cPanel / Plesk / VPS)

More info

    For more information about PHP error logs, visit PHP.net.
Please do not PM me for support.

TalonDOD

Yeah, I tried to start working on that route and godaddy's hosting stuff was still giving me weird errors that wouldn't let me get where I needed to go, so in a frustrated huff I decided to just start over again.

I got a new site on hostgator which had a one-click install for SMF, and Im just trying to copy the important stuff from my old boards over to the new site.

I appreciate everyones help! 

I'm going to mark this as solved since we did all we could on this side, I think Godaddy is just jacked up.


Steve

Quote from: TalonDOD on November 25, 2021, 09:59:59 PMI think Godaddy is just jacked up.

You and most everyone here.
Please do not PM me for support.

shadav

lmfao what steve said  :laugh:
unfortunately though, hostgator isn't much better either

Shades.

Quote from: shadav on Yesterday at 07:26:24 AMlmfao what steve said  :laugh:
unfortunately though, hostgator isn't much better either
I've had all my sites on hostgator for several years now and have had hardly any problems and when I do they usually help me get it fixed pretty quickly via support chat. Just my experience and opinion. ;)

I use godaddy to buy and sell domain names when their site works lol but never tried their hosting service! ???  8)

ShadesWeb.com - Custom Logos
https://shadesweb.com

BikerHound.com - Sniffing out the road ahead
https://bikerhound.com

Dream as if you'll live forever; Live as if you'll die today. - James Dean

shadav

eh maybe hostgator has gotten better over the years 🤷�♀️, or you're just lucky  :P

yeah for domains I've heard godaddy is ok, but for hosting I wouldn't ever go near them with a 10 foot pole

Advertisement: