Posted: April 19, 2024 at 3:39 pm
|
The REGISTRATION CSV REPORT button at the bottom of an event registration creates a CSV file that automatically exports to the browser downloads folder. It works properly when the registrations are rendered from the EVENT ESPRESSO EVENTS page. However, when bypassing the EVENTS page and using the EVENT ESPRESSO REGISTRATIONS page, an error develops when trying to use the REGISTRATION CSV REPORT button. I get a “502 Bad Gateway, nginx” error. I am not trying to export the entire 8000 registrations. I typically filter month by month. So, I can see that the list will be rather short for June 2023 (the start of our fiscal year). Not many events are purchased during June. I have tried filtering successive months with instant Gateway errors. Is this re-creatable on your end, or do I have a misconfiguration with my hosting system? |
|
|
As we approach the close of our fiscal year, I prefer exporting the Registration reports for analysis in a monthly display fashion, because the action has an EVENT NAME filter (which is missing when exporting CSV by Event). The Event Name filter is inserted after the REGISTRATION ID column and in front of the FIRST NAME column. This is a valuable column when analyzing lots of events listed by category. |
|
|
Hello, Let me try to recreate the issue. Can you tell us your site PHP version, EE version and and database. Can you also shoot video on the problem you experience? you can use loom to do that. Have you also tried if there’s any possible plugin conflict? and if you also receive any error log? Check this article here. thanks |
|
|
I went through the process of deactivating all the non-EE plugins. I try to keep a minimum of plugins because this is meant to be primarily an Event E-Comm website: https://PatrollerSchool.org We are lucky that our events follow a season. The last transaction is recorded on May 5th, and the new selling season begins mid-June. This gives me five weeks for overhauling and site maintenance, such as hosting site upgrades. I will upgrade MySQL and PHP in May. Today, we use the following versions:
WordPress Version 6.5.2 Divi Version: 4.25.0 MySQL version 5 PHP 7.4 A video won’t help because I just set the Month picker to JUNE2023, EE produces the following long URL and the “502 Bad Gateway” error. See if the URL is assembling correctly:
|
|
|
NEW INFORMATION I decided to explore all the choice possibilities other than Month/Year from the picker box… The REGISTRATION CSV REPORT button produces perfect export files when I select the following text link choices offered by EE:
Today – Apr 20, 2024(0) Yesterday – Apr 19, 2024(0) This Month(79) Incomplete(77) Trash(0) No Bad Gateway errors. I got the entire database of 7399 registrations, from which I was able to trim it down to my requirement of June2023 to April2024. I got what I need for end-of-season analysis. So then I tried using picker choices from the pull-down boxes. All three boxes produce that Bad Gateway error. These are the picker boxes:
All Categories Select Status |
|
|
Is it valuable to compare and contrast the URL produced by each? This URL for the link THIS MONTH (79) worked with the REGISTRATION CSV REPORT button:
This is the identical filtration, using the picker box selecting APRIL2024. I click the filter button and see 79 lines of registration rendered on the page. This is the failed URL that is generated along with the 502 Bad Gateway error:
|
|
|
Hi there, Firstly, thank you for the thorough testing and reporting 🙂 5XX errors aren’t thrown from within EE itself, those are server-side errors and 502 Bad Gateway means the server received an invalid response from upstream (could be a proxy, load balancer etc which then received an error from the server processing the request). Now that’s not to say EE isn’t causing the error (obviously it is here) but, I’m not getting any errors on 5.0.19.p when testing the same steps so EE is likely triggering something on the server here, for example, a mod_sec rule which doesn’t like the CSV request with the filters set. Can you test the ‘old’ CSV reporting on the site, please? To do that, just add:
to your site’s That disables the ‘batch’ processing but I’d like to see if that also triggers a 502 if possible. |
|
|
I made the edit into wp-config.php and the host server tried to process the JUNE2023 filtered CSV query string. This time, the behavior took 2 minutes to time out and returned a 500 Server Error: It looked different. I recognized it as a server error, whereas the Gateway Error occurs instantly upon button press. Thanks for the suggested probe… |
|
That is likely a timeout error, but I wouldn’t expect a timeout with those lower numbers of registrations (the ‘old’ system had issues from about 2000 registrations up, it was heavily dependant on the server in use).
I assumed the 502 errors were instant earlier, that’s part of why I suspect is hitting a mod_sec rule. Request initiates and is instantly blocked, usually to a 404 or 403 but not always. Ok, lets try some error logging and see where that gets us. In your wp-config.php file, add this: https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug That snippet replaces this single line that is usually already set in that file: That tells the serve to log error within With that code in place, try again (you can try both with and without |
|
|
I set up the DeBug TRUE snippet, but I can not find ../wp-content/debug.log It does not seem to be creating the log file. Is there another place to look? Is it putting the log elsewhere? |
|
|
Hello, Just to be sure, did you use whole blocked here. After adding the code, you have to recreate the issue, by processing the JUNE2023 filtered CSV query string. then you go and check the log and send it to us. thanks |
|
|
Yes, I used the entire block and left it in. After your message, I decided to force a detectable bug in another location. This produced the DEBUG LOG in the correct location. This morning, I logged into the admin EE panel. Went to registrations. Filtered for JUNE2023, then July thru October. The 502 Gateway Error instantly poped up, but upon opening the debug log, nothing was added from EE. This is what I pulled off the log: It ended without recording errors… |
|
|
A 502 gateway error usually means the server is down, not necessarily running into any error from code or conflicts. Can you check your hosting about this? You also try this troubleshooting method: Try temporarily deactivating all other plugins on the site and try those links again. If no Bad Gateway error with all other plugins deactivate, you reactivate the other plugins one-by-one until the you see the error again. You can check similar thread here. thanks |
|
You must be logged in to reply to this support post. Sign In or Register for an Account
