Jump to content

JoieDeMort

Members
 View Profile  See their activity

  • Posts

    38

  • Joined

  • Last visited

 Content Type 

Posts posted by JoieDeMort

  2. Email Piping No Longer Working

    in Support

    Posted

    Nothing has changed with cPanel in the last 2 weeks or php since late last year.

     

    Server admin has a question:

    "One quick question, is there a process that is supposed to happen (it looks like the dispatchCLI function should make some http request, I assume this should make some entries in your tracking system or generate an action. Is this happening but the error is logged (and the bounce message sent) or is this not happening and the bounce message is sent."

     

    I don't see anything in the Blesta logs.

     

    Recreating the pipe forwarder in cPanel didn't help.

  3. Email Piping No Longer Working

    in Support

    Posted

    Thanks for the replies!

     

    Everything is still set up as it was, with the settings just as in the referenced email piping docs. No changes have been made to anything except for whatever cPanel automatically upgraded. I'm trying to run that angle down.

  4. Email Piping No Longer Working

    in Support

    Posted

    Since that thread in 2013 (http://www.blesta.com/forums/index.php?/topic/1017-email-piping/), I've successfully used the pipe1.php. Today, I discovered that it's no longer working; I can't figure out anything which has recently changed on the server recently which could cause this. When I use cPanel to set it up with the default pipe.php, it also doesn't work. Changing default permissions from 644 to the 744 pipe1 used (or even to 777) adds additional errors shown below. Any ideas? No errors are logged in Blesta, obviously.

     

     

      pipe to |/home/account_name/public_html/secure/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1

        generated by sales@account_name.com

        local delivery failed

      pipe to |/home/account_name/public_html/secure/plugins/support_manager/pipe1.php plugin/support_manager/ticket_pipe/index/1

        generated by sales@account_name.com

        local delivery failed

     

    The following text was generated during the delivery attempt:

     

    ------ pipe to |/home/account_name/public_html/secure/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1

           generated by sales@account_name.com ------

     

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 1: ?php: No such file or directory

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 2: /**: No such file or directory

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 3: access-logs: command not found

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 4: access-logs: command not found

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 5: access-logs: command not found

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 6: blestauploads/: is a directory

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 7: =: command not found

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 9: try: command not found

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 10: syntax error near unexpected token `dirname'

    /home/account_name/public_html/secure/plugins/support_manager/pipe.php: line 10: `           include(dirname(__FILE__) . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . ".." . DIRECTORY_SEPARATOR . "lib/init.php");'

  11. Upgraded Server To Php 5.5 After Upgrading Blesta To 3.5 Yesterday

    in Support

    Posted

    Thanks so much for your input! Apparently when the support tech updated php, easyapache integration wasn't enabled within litespeed, so the server php version was updated but the litespeed php version was not. Once that was fixed, everything works as it should

     

    Again thanks for all of your input! Hopefully, this experience goes in the back of your mind as something to check next time something weird happens associated with litespeed.

  13. Upgraded Server To Php 5.5 After Upgrading Blesta To 3.5 Yesterday

    in Support

    Posted

    Now that EA is finished, no more 500 error.

     

    Back to this error:

    file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/usr/local/lib/php/extensions/no-debug-non-zts-20121212/../../../../../../home/ioncube/ioncube_loader_lin_5.3.so) is not within the allowed path(s): (/home/xxxxxxx:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp) on line 2 in /home/xxxxxxx/public_html/blestainstalldirectory/app/app_model.php

     

    Any ideas?

  15. Upgraded Server To Php 5.5 After Upgrading Blesta To 3.5 Yesterday

    in Support

    Posted

    So I feel stupid right now.

     

    I upgraded blesta yesterday to 3.5. Then this morning I upgraded the server to 5.5 from 5.3 totally forgetting about the hotfix issue.

     

    I tried to access the dashboard this morning and got this error:

    file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/usr/local/lib/php/extensions/no-debug-non-zts-20121212/../../../../../../home/ioncube/ioncube_loader_lin_5.3.so) is not within the allowed path(s): (/home/xxxxxxx:/usr/lib/php:/usr/php4/lib/php:/usr/local/lib/php:/usr/local/php4/lib/php:/tmp) on line 2 in /home/xxxxxxx/public_html/blestainstalldirectory/app/app_model.php

     

    Of course, I then remembered the hotfix. I tried uploading those files then with no resolution. Then I reuploaded the entire blesta 3.5 and tried to run upgrade. Still gives me that error.

     

    What do I do now to resolve this? php is not my forte.

  18. Premadekb.com: Blesta Ready-Made Cpanel Knowledgebase Articles + Images

    in The Marketplace

    Posted

    They really do look nice.

     

    However, I hit "pause" on ordering when I saw some grammar issues like this: at least 2 errors per line.

     

    article.gifWhat can i do after purchase Dedicated IP?
    If you're already purchase Dedicated IP then you need to change your Domain Name Server.  ...

     

     

    Another random click brought me to this:

     

    article.gifRules on SPAM emails
    We Strickly Prohibited Spaming on our server.   If you're send any type of spam email then...
    Views: 351

    article.gifSeprate Invoice for my Services?
    If you want to get a seprate invoice for your active services then open a ticket with us and we...

     

     

    I suggest getting someone to edit these to look absolutely professional. You're almost there.

  19. Order Forms Don't Show Package Selection

    in Support

    Posted

    To follow up for future viewers:

     

    The AJAX templates are designed to scroll to past the selection boxes.

     

    This disappoints me because my understanding is that long form templates are higher converting than multi-step. However, the AJAX templates are the only long form templates included, and because of how they're designed, you can't link to the AJAX template for people to make a selection and review. This appears to me to require duplicating the selection content outside of Blesta.

     

    I know I didn't type that clearly. Sorry.

  20. Order Forms Don't Show Package Selection

    in Support

    Posted

    When anyone goes to the order forms (long style) with the boxes on top, the viewer is already scrolled past the selection boxes and see only the monthly/annual configuration at the top of the browser.

     

    I must be missing something; how do I send the viewer to the page so that the selection boxes are at the top of the browser screen and not hidden?

     

    Thanks!

  23. How To Prevent? Cpanel Useraccount@serverhostname Showing As The Return Address In Email Tickets

    in Support

    Posted

    I have php email piping active based on the php fix in another thread, so email piping works just great.

     

    However, every ticket email goes to clients as "cPanelusername@fullserverhostname on behalf of whicheverdepartment@mydomain.com"

     

    I'd very much like to keep the domain's cPanel username private! How can this be done?

     

    Also, in the email headers, it shows the php piping string. Hopefully that will never be a security issue . . .

×
×
  • Create New...