Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • nevermind… I tried a couple things and not sure which one helped.
    1) I added the hostserver name to the list of Authorized Javascript Origin URLs (in addition to the DNS URL for the website
    2) I re-approved the permission on Google

    It then successfully copied all 5 backups to the Google Drive.

    Happy Day! 😉

    • This reply was modified 8 years, 11 months ago by wavggg.

    Identical to the previous gentleman (who apparently is still unresolved)… we just now installed, verified, paid worship on the Google Drive alter, etc. to establish all the right links, IDs, Secret Mason handshakes, etc., with bi-directional confirmation that all digital entities named were approved with each other to have mutual internet “sex”… so PLEASE don’t ask me about the obvious!

    Nope – same message in the Updraft log file, “Google Drive: Account is not authorized.”

    I would love to be able to see the command line which goes out from Updraft directly ahead of that Google Drive response…

    The good news is that Updraft DID conclude all the backups which I immediately downloaded to my local PC. Yet, still, I expect it to perform as advertised/ promised (yes even without a bloody warranty for free software.)

    So whom amongst you are the mega-guru troubleshooter to identify where in the communication chain this pending ‘nuptial’ is falling flat and being rejected by the future ‘in-laws’ at Google – and how to provide the appropriate ‘dowry’ to satisfy the ‘jealous father-in-law’ and lead us into pure and holy ‘consummation’?

    Bring it on! – As a 40 year veteran of electronics/software troubleshooting I hope to be amazed at your Ninja skills to knock this down in 24 hours! If you do well I’ll post it on one of our blogs… 😉 Ok?

    Best o’ luck and thanks in advance…
    greg da’goose
    https://gallantgoose.com
    see attached log:
    <script src=”https://pastebin.com/embed_js/eS3zNUqW”></script&gt;

    wavggg

    (@wavggg)

    Hi Wayne –

    to the extent that i just showed you the two problems are the same issue – just a different threshold.

    i just showed you by gradually increasing the content (size of the email), i could get Postie to crash.

    greg

    wavggg

    (@wavggg)

    Hi Wayne –

    Test 15.2 DID NOT produce another mystery post named “tmptitle”

    now running Test-15.3
    (text only – double the words in Test-15.2)

    verified connection (see below)
    ran debug
    sat for 15 seconds saying, “waiting for pixel.wp.com” (it used to say waiting for http://www.gallantgoose.com)
    locked up so my firefox browser lost connection with the server
    reported:

    File not found
    Firefox can’t find the file at https://www.gallantgoose.com/wp-admin/admin.php?page=postie-settings.
    Check the file name for capitalization or other typing errors.
    Check to see if the file was moved, renamed or deleted.

    I anticipate there will be another mystery posting called “tmptitle” as soon as the server resets and I can log back in (maybe 5-10 min)…

    same results since March 12/13 – all as before….

    In the PREVIOUS debug.log (Test 15.2) – I saw things which appeared to be messed up with regard to your variables… it looked like it was placing the email text in those fields – MUCH TOO MUCH!

    I WILL FORWARD YOU A COPY OF TEST-15.2 AND TEST-15.3 SO YOU CAN SEE THE MINIMAL DIFFERENCE IN CONTENT.

    greg

    wavggg

    (@wavggg)

    Hi Wayne –

    Test 15.1 DID NOT produce another mystery post named “tmptitle”

    now running Test-15.2
    (text only – double the words in Test-15.1)

    verified connection (see below)
    ran debug
    immediately began processing
    produced debug report (see at bottom) – did not lock up
    Posted email (view here) https://www.gallantgoose.com/test-15-2/

    In the debug.log – I see things which appear to be messed up with regard to your variables… looks like its placing the email text in those fields!

    greg

    wavggg

    (@wavggg)

    Hi Wayne –

    Test 15 DID produce another mystery post named “tmptitle” even though it crashed
    the content of the post (as all previous) is one word – “tmpPost”

    now running Test-15.1
    (text only – fewer words than Test-15)

    verified connection (see below)
    ran debug
    immediately began processing
    produced debug report (see at bottom) – did not lock up
    Posted email (view here) https://www.gallantgoose.com/test-15-1/

    greg

    wavggg

    (@wavggg)

    Hi Wayne –

    reinstalled and activated Postie Support
    running Test-15

    verified connection (see below)
    ran debug
    sat for 15 seconds saying, “waiting for pixel.wp.com” (it used to say waiting for http://www.gallantgoose.com)
    locked up so my firefox browser lost connection with the server
    reported:

    File not found
    Firefox can’t find the file at https://www.gallantgoose.com/wp-admin/admin.php?page=postie-settings.
    Check the file name for capitalization or other typing errors.
    Check to see if the file was moved, renamed or deleted.

    I anticipate there will be another mystery posting called “tmptitle” as soon as the server resets and I can log back in (maybe 5-10 min)…

    same results since March 12/13 – all as before….

    greg

    wavggg

    (@wavggg)

    Hi Wayne:

    You’ve been assisting me for 16 days on the issue of Postie no longer functioning on my WordPress installation hosted by Hostcentric.

    I came across this forum post by ghawblin and realized it sounds familiar. In addition to the website crashes we are experiencing when executing a Process Email or Debug – the “teptitle” postings that ghawblin describes above also appear in our log of posts.

    I had presumed that these were testing attempts by the tech support people at Hostcentric; however, upon looking at the Author field for each, it attributes them to me! And each corresponds to an attempt to post via Postie, even though the system crashes and locks me out.

    I hope adding this information to the forum is helpful to us all.

    thanks!
    greg groeper

Viewing 8 replies - 1 through 8 (of 8 total)