I have a Internal Server error

For more troubleshooting information:
– WordPress 5.2.4
– Active theme: Twenty Twelve
– Active Plugin

Akismet Anti-Spam
Version 4.1.2 by Automattic
All-in-One WP Migration
Version 7.8 by ServMask
All-in-One WP Migration Unlimited Extension
Version 2.22 by ServMask
BackWPup Pro
Version 3.6.10 by Inpsyde GmbH
Cloudflare
Version 3.4.1 by John Wineman, Furkan Yilmaz, Junade Ali (Cloudflare Team)
Crowdsignal Polls & Ratings
Version 2.1.2 by Automattic, Inc.
Gutenberg
Version 6.7.0 by Gutenberg Team
Hangeul Web Fonts
Version 0.4.2 by miracl2l22
Health Check & Troubleshooting
Version 1.4.2 by The www.remarpro.com community
Jetpack by WordPress.com
Version 7.8 by Automattic
Press This
Version 1.1.1 by WordPress Contributors
Shortlinks for Jetpack sharing buttons
Version 1.0 by Jeremy Herve
VaultPress
Version 2.0.1 by Automattic
VideoPress
Version 1.5.6 by Automattic, Niall Kennedy, Joseph Scott, Gary Pendergast
WP-Bigfoot
Version 1.0.1 by Roger Stringer
WP Mail SMTP
Version 1.7.0 by WPForms

– Server Configuration

Web server
Apache/2.4.41 (Ubuntu)
PHP version
7.3.11-1+ubuntu18.04.1+deb.sury.org+1 (Supports 64bit values)
PHP max input variables
1000
PHP time limit
300
PHP memory limit
256M
Max input time
60
Upload max filesize
100M
PHP post max size
100M
Extension
mysqli
Server version
5.7.27-0ubuntu0.18.04.1

@hansollkim I can see you are using an alternative AMP plugin at present. If you want to test again using this plugin you can activate and enable amp in transitional or standard mode. You can then temporarily deactivate other plugins one by one before checking for the error again.

Nothing stands out from your server configuration and you are using an amp compatible theme, so it’s worth testing with other plugins deactivated, in particular other amp plugins, which may cause conflicts.

A similar issue was raised previously on GitHub, which was resolved by installing a PHP extension.

Yes, I have no other option other than installing another plugin to continuously serve AMP pages. I’ll disable that and other plug-ins, but I think I’ve done already done turned off *all* plugins except AMP. Anyway, it’s worth to take another shot. I’ll keep it on the task list.

Besides, I’ll refer to the GitHub post you’ve given, and I’ll keep you posted.

Thanks.

Sorry for the bad news. The turning off all other plug-in wasn’t helped, with “iconv” in PHP install and running. It shells out 500 server error. Since the AMP page is default via Twitter and some other application, I need to turn off your plugin and revert to an alternative one because your plug-in displays only 500 error to the visitor. But I used your plugin for a long time. I want to keep using. Please follow me to keep troubleshooting.

@hansollkim Thanks for the update. In relation to your old references/links to your AMP versions on social media any such amp links will revert to your non AMP.

Can you let me know of the following:
– Do you know when the issue started occurring (after a plugin update, hosting change etc)?
– What mode were you previously using?
– Is the same issue occurring with an alternative theme active (and plugins deactivated)?
– Can you check for the same issue by reverting to PHP v7.2x

If you want to activate the plugin in transitional mode (with other amp plugins deactivated) we might be able to spot something which may be impacting rendering. You can also set the following in your wp-config.php file:

define('WP_DEBUG', true);
define( 'WP_DEBUG_DISPLAY', true );

1. I’ve suffered severe server outage, so I reverted the server from the backup provided from Linode(hosting provider), and I overwrite it with the whole WP site backup from made with Automattic’s VaultPress Backup. FYI I’ve re-installed AMP manually.
2. So-Called “Classic” mode, what we now call it now?
3. I’ve tested with another www.remarpro.com theme(twenty twelve), but not with all plugin turned off.
4. I have no confidence to roll back to PHP 7.2.

I’ll turn transitional mode and debug mode on and check how it goes. Please allow me some time.

• This reply was modified 5 years, 4 months ago by hansollkim. Reason: I missed mentioning VaultPress

I’ve tested all plugins off and made it transitional mode. I have a this error

Transitional mode activated! However, there was an error when checking the AMP validity for your site. URL validation failed to due to the absence of the expected JSON-containing AMP_VALIDATION comment after the body.

and Google’s AMP validator failed to pass, both transitional and reader mode.

WordPress doesn’t create any log file at wp-content directory. Is there another location it saves the log?

@hansollkim Do you have any other sites hosted on the same server you can check with? It would be useful to check with the AMP plugin activated.

You can use one of the many plugins to create a backup/staging site to recreate your site which we can test with. Looking at your PHP info I don’t see anything out of the ordinary so it would be worth testing another site or a duplicste on the same server.

No, I’m currently only hosting just one site on my server, and do not know multi-site configuration currently. But I run another server with WordPress. It’s not entirely the same(I did the same configuration setting, but not a clone). I will try it whether it is working.

Anyway. It is awkward not working.

• This reply was modified 5 years, 4 months ago by hansollkim.

I found that the alternative server is working very well with the AMP plugin. But this server is almost fresh, and the server with problem hosting data dates back to 14 years ago. We need to take different approaches for both servers. We could consider complete re-deployment of the server, but it would be a painful and daunting process.

• This reply was modified 5 years, 4 months ago by hansollkim.

@hansollkim Nice troubleshooting, as it’s server related I will close this support topic. Check and see if there are any updates to your server, which from checking your phpinfo and what you’ve shared I don’t see any issues.

Okay, If all of these are sever related, where should I talk to, In your opinion?
I really like your plugin for a long time, and wish to use it continue as possible. Maybe I proved another server is okay, but that does not separate clearly this malfunction as server trouble.

@hansollkim We would love for you to be using the plugin also. If it’s working on your other server then we may need more information from your current hosting environment.

@westonruter do you have any ideas on how we could investigate further?

I just downgraded PHP to PHP 7.2.24-1+ubuntu18.04.1+deb.sury.org+1. There’s some validation error is shown, but anyway plugin is working! Am I wrong to upgrade PHP 7.3? or made a mistake while upgrade? or a simple compatibility issue? How do you think?