jasonfb

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter jasonfb

    (@jasonfb)

    I don’t control the server’s technology (although I do rent it). It is hosted on Plesk, a self-contained fully managed hosting platform that is quite excellent in my opinion (yes it runs on IIS, but I only interact with it through the web interface).

    it’s not a matter of “please use” I don’t have the luxury of simply “using” one stack or another. this system is the hands-down the cheapest, fastest, most effective way to deploy WordPress I know of, except of course for bugs that show up on IIS and not on Linux.

    I’ve hosted WordPress on Linux many times in my life— typically winds up being a huge time-suck and headache, I spend more of my time worrying about devops and sysadmin than I do writing blog posts.

    What I want to do is write blog posts. I am a writer. I do not care about tech stacks and platforms and all that– I just want that part to work and not be a headache.

    so my choice to use IIS is not casual— it is based on cost, money, time, speed, efficiency.

    Thread Starter jasonfb

    (@jasonfb)

    On another blog (I have many blogs) upgrade from 2.4 to 2.4.1 also crashes

    Update Failed: <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”&gt; IIS 8.0 Detailed Error – 500.0 – Internal Server Error <!– body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;} a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;} h4{font-size:1.2em;margin:10px 0 5px 0; }#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:”trebuchet MS”,Verdana,sans-serif; color:#FFF;background-color:#5C87B2; }#content{margin:0 0 0 2%;position:relative;} .summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} .content-container p{margin:0 0 10px 0; }#details-left{width:35%;float:left;margin-right:2%; }#details-right{width:63%;float:left;overflow:hidden; }#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF; background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal; font-size:1em;color:#FFF;text-align:right; }#server_version p{margin:5px 0;} table{margin:4px 0 4px 0;width:100%;border:none;} td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;} th{width:30%;text-align:right;padding-right:2%;font-weight:bold;} thead th{background-color:#ebebeb;width:25%; }#details-right th{width:20%;} table tr.alt td,table tr.alt th{} .highlight-code{color:#CC0000;font-weight:bold;font-style:italic;} .clear{clear:both;} .preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;} –> HTTP Error 500.0 – Internal Server Error C:\Program Files (x86)\Plesk\Additional\PleskPHP74\php-cgi.exe – The FastCGI process exceeded configured activity timeout Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. Things you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server’s machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. Detailed Error Information: Module   FastCgiModule Notification   ExecuteRequestHandler Handler   PHP-php Error Code   0x80070102 Requested URL   https://blog.momeas.com:443/wp-admin/admin-ajax.php Physical Path   C:\Inetpub\vhosts\datatravels.com\blog.momeas.com\wp-admin\admin-ajax.php Logon Method   Anonymous Logon User   Anonymous More Information: This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error. View more information » Microsoft Knowledge Base Articles: 294807

    Thread Starter jasonfb

    (@jasonfb)

    I then re-deleted (for a second time) the wp-content/plugins/amazon-s3-and-cloudfront folder and then again tried to re-install WP Offload Media lite

    this time it installed without error

    also then it activated without error

    and I see that it has correctly picked up my previous settings for my S3 bucket + cloudfront CDN

    (I guess these settings were saved in the DB because I cleaned out the plugin folders/files as described above)

    Thread Starter jasonfb

    (@jasonfb)

    Now i’m unable to install 2.4.1

    Installation failed: <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”&gt; IIS 8.0 Detailed Error – 500.0 – Internal Server Error <!– body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;} a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;} h4{font-size:1.2em;margin:10px 0 5px 0; }#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:”trebuchet MS”,Verdana,sans-serif; color:#FFF;background-color:#5C87B2; }#content{margin:0 0 0 2%;position:relative;} .summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} .content-container p{margin:0 0 10px 0; }#details-left{width:35%;float:left;margin-right:2%; }#details-right{width:63%;float:left;overflow:hidden; }#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF; background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal; font-size:1em;color:#FFF;text-align:right; }#server_version p{margin:5px 0;} table{margin:4px 0 4px 0;width:100%;border:none;} td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;} th{width:30%;text-align:right;padding-right:2%;font-weight:bold;} thead th{background-color:#ebebeb;width:25%; }#details-right th{width:20%;} table tr.alt td,table tr.alt th{} .highlight-code{color:#CC0000;font-weight:bold;font-style:italic;} .clear{clear:both;} .preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;} –> HTTP Error 500.0 – Internal Server Error C:\Program Files (x86)\Plesk\Additional\PleskPHP73\php-cgi.exe – The FastCGI process exceeded configured request timeout Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. Things you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server’s machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. Detailed Error Information: Module   FastCgiModule Notification   ExecuteRequestHandler Handler   PHP-php Error Code   0x80070102 Requested URL   https://blog.jasonfleetwoodboldt.com:443/wp-admin/admin-ajax.php Physical Path   C:\Inetpub\vhosts\datatravels.com\blog.jasonfleetwoodboldt.com\wp-admin\admin-ajax.php Logon Method   Anonymous Logon User   Anonymous More Information: This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error. View more information » Microsoft Knowledge Base Articles: 294807

    Thread Starter jasonfb

    (@jasonfb)

    see image

    image for bug report?https://www.ads-software.com/support/topic/upgrade-to-version-2-4-crashes/

    Thread Starter jasonfb

    (@jasonfb)

    Attempting on a different site from version 2.3.2 to version 2.4.1 (notice that the error above was for version 2.4.0)

    same problem

    Update Failed: <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd”&gt; IIS 8.0 Detailed Error – 500.0 – Internal Server Error <!– body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 5px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;word-break:break-all;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px; font-weight:bold;font-size:1em;} a:link,a:visited{color:#007EFF;font-weight:bold;} a:hover{text-decoration:none;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;} h4{font-size:1.2em;margin:10px 0 5px 0; }#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:”trebuchet MS”,Verdana,sans-serif; color:#FFF;background-color:#5C87B2; }#content{margin:0 0 0 2%;position:relative;} .summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} .content-container p{margin:0 0 10px 0; }#details-left{width:35%;float:left;margin-right:2%; }#details-right{width:63%;float:left;overflow:hidden; }#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF; background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal; font-size:1em;color:#FFF;text-align:right; }#server_version p{margin:5px 0;} table{margin:4px 0 4px 0;width:100%;border:none;} td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;} th{width:30%;text-align:right;padding-right:2%;font-weight:bold;} thead th{background-color:#ebebeb;width:25%; }#details-right th{width:20%;} table tr.alt td,table tr.alt th{} .highlight-code{color:#CC0000;font-weight:bold;font-style:italic;} .clear{clear:both;} .preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;} –> HTTP Error 500.0 – Internal Server Error C:\Program Files (x86)\Plesk\Additional\PleskPHP73\php-cgi.exe – The FastCGI process exceeded configured activity timeout Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed. Things you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server’s machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here. Detailed Error Information: Module   FastCgiModule Notification   ExecuteRequestHandler Handler   PHP-php Error Code   0x80070102 Requested URL   https://blog.jasonfleetwoodboldt.com:443/wp-admin/admin-ajax.php Physical Path   C:\Inetpub\vhosts\datatravels.com\blog.jasonfleetwoodboldt.com\wp-admin\admin-ajax.php Logon Method   Anonymous Logon User   Anonymous More Information: This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error. View more information » Microsoft Knowledge Base Articles: 294807

    Thread Starter jasonfb

    (@jasonfb)

    On one site where I experienced this I have these plugins now (after the upgrade error–you’ll note WP Offload Media Lite is now showing upgrade to 2.4.1)

    Akismet Anti-Spam
    Settings | Deactivate | Troubleshoot
    Used by millions, Akismet is quite possibly the best way in the world to protect your blog from spam. Your site is fully configured and being protected, even while you sleep.

    Version 4.1.6 | By Automattic | View details
    Select Embed React app
    Embed React app
    Deactivate | Troubleshoot
    Embedding a React Application to WordPress post

    Version 1.0.1 | By [email protected] | View details
    Select Google XML Sitemaps
    Google XML Sitemaps
    Deactivate | Troubleshoot
    This plugin improves SEO using sitemaps for best indexation by search engines like Google, Bing, Yahoo and others.

    Version 4.1.0 | By Arne Brachhold | View details | Settings | FAQ | Support
    Select Health Check & Troubleshooting
    Health Check & Troubleshooting
    Health Check | Deactivate | Troubleshoot
    Checks the health of your WordPress install.

    Version 1.4.4 | By The www.ads-software.com community | View details
    Select Insert Headers and Footers
    Insert Headers and Footers
    Deactivate | Troubleshoot
    Allows you to insert code or text in the header or footer of your WordPress blog

    Version 1.4.6 | By WPBeginner | View details
    Select Open Graph and Twitter Card Tags
    Open Graph and Twitter Card Tags
    Settings | Deactivate | Troubleshoot
    Improve social media sharing by inserting Facebook Open Graph, Twitter Card and SEO Meta Tags on your WordPress website pages, posts, WooCommerce products, or any other custom post type.

    Version 3.0.0 | By Webdados | View details
    Select Social Login, Social Sharing by miniOrange
    Social Login, Social Sharing by miniOrange
    Deactivate | Troubleshoot
    Allow your users to login, comment and share with Facebook, Google, Apple, Twitter, LinkedIn etc using customizable buttons.

    Version 7.3.9 | By miniOrange | View details
    There is a new version of Social Login, Social Sharing by miniOrange available. View version 7.3.10 details or update now.

    Select WP Google Maps
    WP Google Maps
    Get Pro Version | Settings | Map Editor | Deactivate | Troubleshoot
    The easiest to use Google Maps plugin! Create custom Google Maps with high quality markers containing locations, descriptions, images and links. Add your customized map to your WordPress posts and/or pages quickly and easily with the supplied shortcode. No fuss.

    Version 8.0.25 | By WP Google Maps | View details
    Select WP Mail SMTP
    WP Mail SMTP
    Settings | Premium Support | Deactivate | Troubleshoot
    Reconfigures the wp_mail() function to use Gmail/Mailgun/SendGrid/SMTP instead of the default mail() and creates an options page to manage the settings.

    Version 2.2.1 | By WPForms | View details
    Select WP Offload Media Lite
    WP Offload Media Lite
    Settings | Deactivate | Troubleshoot
    Automatically copies media uploads to Amazon S3, DigitalOcean Spaces or Google Cloud Storage for storage and delivery. Optionally configure Amazon CloudFront or another CDN for even faster delivery.

    Version 2.4 | By Delicious Brains | View details

    Thread Starter jasonfb

    (@jasonfb)

    Umm.. no I don’t think so

    Thread Starter jasonfb

    (@jasonfb)

    this happened on two separate WP sites for me.

    On one site (blog.momeas.com), once I removed the .maintenance file the site came back online OK

    ON the other site, when I removed the .mainteannce file the site came back but the plugin was disabled.

    I then tried to re-install the plugin, but couldn’t while the folders at /wp-content/plugins/ still existed. (the plugins installer told me the folder was already there)

    I then removed the folder completely and attempted again to reinstall the plugin

    (no changes were made to the database)

    this time it installed correctly and my settings appeared to be persisted (I guess because I made no changes to the database the settings were already in the DB)

    Thread Starter jasonfb

    (@jasonfb)

    hmmm… you mean just go back and click “Save” ? Let me try another time

    Thread Starter jasonfb

    (@jasonfb)

    I am still unable to get this to work. I upgraded the plugin to Version 1.15.1 but I am still unable to see the Access-Control-Allow-Origin to show up on my /feed URL

    Thread Starter jasonfb

    (@jasonfb)

    I will look again

    jasonfb

    (@jasonfb)

    @eivindert — what did you do to solve the problem?

    Thread Starter jasonfb

    (@jasonfb)

    however, I was able to fix this by deleteting records in my wp_options table, specifically I deleted all of the records appeared to be created by this plug-in — about 280 records, with option_names including things like “thechamp” and “champ” and “mo_openid_” and “mo_login_” and “_site_transient_” and others

    When did this, De-activated, then Deleted, then Re-installed, then re-activated, the plugin appears to have returned to working and the Facebook login now works and comes through with the correct App ID

    Thread Starter jasonfb

    (@jasonfb)

    still happens when upgraded to 7.3.1

Viewing 15 replies - 1 through 15 (of 18 total)