notmateo
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: 502 Error from Imagic when uploading large images (Plus it’s slow)@wpmudevsupport12 Nope none. This is an extremely clean WordPress. No content, no plugins (except the mu-plugin), no downloaded themes.
I don’t really think this is at all a database issue. When I get the free time I will still practice due diligence and check of course, but it should be safe to assume that nothing useful will be there.
Forum: Fixing WordPress
In reply to: 502 Error from Imagic when uploading large images (Plus it’s slow)@piecebutechsup Thanks for the tip. I gave it a try and it’s…. also marginally faster. I also am testing a new reverse proxy which is helping marginally as well. This plus the tips given above and the 32GB of RAM has the site still running oddly slow on uploads.
I have a client who’s consistently uploading this kinda media and it’s a bit painful for them. Are there other image processors I can be using here? Or better batching somehow?
Forum: Fixing WordPress
In reply to: 502 Error from Imagic when uploading large images (Plus it’s slow)@piecebutechsup I followed up on this and tried to max out the performance- I gave WordPress as much wiggle room as I can with like 32GB of RAM (PHP and WordPress) and it worked better but definitely still not good. I forced Imagick to use 12 cores and like 4GB of RAM also but no success.
I set max execution time to unlimited and something interesting happened; the page gave the same error but the console logged a 504 instead. Meanwhile I was watching server resources and WP was still processing something. I waited till it was done and refreshed. Usually after the max_execution_time it gives up and stops using CPU so I refresh and the image is there but clicking it is blank and it’s thumbnail takes obscenely long to load since it’s using a full size version. Now I can at least get the large file to upload but it still takes a very long time.
Is there something I’m missing to getting the proper performance out of this?? I’m using PHP-FPM 8.3 on a 2x 48-core Xeon Platinum 8168 with 256GB of RAM. Or at least that’s where the image processing is happening and causing issues. There’s a proxy server between them but it seems to not have any issues until it has to load all those no-thumbnail images that are 10MB each concurrently.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationAppreciate the links and information. If the answer ends up being something simple, I’ll be sure to post it here so others may find it/support staff can have that little extra bit of knowledge.
Thanks again
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationNever said anything about posting them on the forum in broad public. Was going to send them to the support staff if they needed it, for a test site, through private means. Which is pretty standard in WordPress support. 🤷♂️
No worries. I won’t consider giving support a testing log in on these forums anymore. Thanks.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installation>The issue is likely related to Bunkerweb’s default security headers, request filtering, or proxy configurations.
Thank you for the info. If you want to take a look at the reverse proxy configuration and tell me if you see anything immediately wrong, here it is.
> However, this type of request goes beyond the scope of the support we provide here, as it leans more toward server-level configuration.
But this is also fine and acceptable. Would you be able to point me to any information from the WooCommerce developers on what this Javascript method is failing to grab, I can use that to find my way through other means, as I’m not sure what it’s even trying to grab that it’s nulling on. If you are able to provide that information that’s great, if not, I understand the concept of support scope and understand.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationI’m going to continue to tell you that I am not recording a video. I am tackling this issue in-between working tasks and I have already offered you access to the website itself and will give verbose instructions. I ask that I not be asked anymore about a video.
At any rate I did some digging on my own and switched the server back to our old reverse proxy. We use Bunkerweb now but we used to use NGINX Proxy Manager. I haven’t had the need to use WooCommerce in a long time, but that last time we had a working instance of WP with Woocommerce was with NPM. So I booted it back up to test and the site is now working fine, only on our old reverse proxy.
So now I need to know what settings in our reverse proxy are causing this issue so I can change it.
Here’s a diff of the status page between both reverse proxies, same site: https://www.diffchecker.com/gixw73MJ/
- This reply was modified 1 year, 1 month ago by notmateo.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationForum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationWould it be better if we worked in the test site I made rather than the one where the issue first appeared? The test site isn’t attached to any shared databases or anything of that nature. Then if we can get it to working in this more standardized set up we can see if it works better in the other two sites?
The site was spun up and I went through the initial wp setup (site name, first user, etc), then I removed Hello Dolly and Akismet, then I installed Bricks, then I installed WooCommerce. No site had even been started to be built yet before I tried using WooCommerce and noticed the issue. So this was the first time it was set up on this site.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installation“Or are both the setup wizard being unresponsive and the console error happening together across all setups?”
Yes, this exactly. I’m making the assumption that they’re related which they very well may not be at all. I guess since that’s the first place I would’ve looked myself (since it’s the only error I’m seeing) I assumed they’re related. I put the cart ahead of the horse on that one.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationI am noticing that for whatever reason the stack trace that was copy pasted cut out a lot of information. Not sure when or how that happened.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationYes, I’ve already given the state of all three sites I tested on:
- homrawp_ site: Bricks was enabled at first. When the site didn’t work, I disabled bricks and went back to default, before ever even messaging you guys. No other plugins, default plugins removed, homrawp_ as the prefix but it was the first and only site in the database.
- zaxwp_ site: Bricks was never installed, default plugins were never removed. However it had zaxwp_ as it’s table prefix in a shared database which you guys didn’t like at all.
- Standard testing site: Bricks was never installed, default plugins were never removed, and table prefix was never changed, in a database only for this website- as standard as it really gets.
Here’s the screenshot. Which is really irritating because the only thing in the screenshot is the stack trace that I already sent. http://share.txgr.xyz/u/aziIXk.png (the uploader here isn’t working. Endlessly loads the image but never embeds it)
As stated above, I am experiencing this issue on the fresh install with only WooCommerce installed.
No, I cannot (will not) record a Loom video. I don’t have time to do all that, and this screenshot is literally the only I would show in a video anyways. Me opening this page, then going to the Inspect console.
What are you seeing in the system report?
- This reply was modified 1 year, 1 month ago by notmateo.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationTurning on Debug/Script Debug made this show up after installing (*and activating) WooCommerce: https://pastebin.com/CQDM82V4
This was in a completely fresh and isolated installation. Here’s the status page for this site: https://pastebin.com/5XtK8TZg
- This reply was modified 1 year, 1 month ago by notmateo.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationIt shows up in the console specifically in the setup wizard. I forgot to mention (somehow) that the two buttons to either skip the setup or go to the next page both are completely unresponsive as well, so it’s currently impossible to use woocommerce right now on these installs.
Forum: Plugins
In reply to: [WooCommerce] Uncaught TypeError, on fresh installationI will go ahead and spin up a completely fresh install with its own database and see how that goes first just to completely take these two websites out of the question.
