Recurring Invoices

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #2153
    StuartW
    Participant

    I would like to use the recurring invoice feature. I don’t quite understand how invoice numbers, dates change on later invoices. Is there info apart from the “How To…” section. Many thanks.

    #2154
    RRowley
    Participant

    The invoice number and date are set the same as if you generated a new invoice manually. The invoice is the next available and the data is the current system date.

    #2155
    StuartW
    Participant

    Many thanks that makes sense, I get it now (also just found the render invoice button that confirms it).

    However I cannot email invoice out. I get this reesponse to a curl command
    <html><head>
    <title>401 Unauthorized</title>
    </head><body>
    <h1>Unauthorized</h1>
    <p>This server could not verify that you
    are authorized to access the document
    requested. Either you supplied the wrong
    credentials (e.g., bad password), or your
    browser doesn’t understand how to supply
    the credentials required.</p>
    </body></html>

    My custom.config.ini has:-
    emailHost = mymailserver
    emailSmtpAuth = true
    emailUsername = SameAsLoginName
    emailPassword = passworSetOnMailServer
    emailSmtpPort = 25
    emailSecure = tls
    emailAck = false
    emailUseLocalSendmail = false

    The invoice system is protected by a user and password. How can one authorise the curl request.
    many thanks

    #2156
    RRowley
    Participant

    Your issue will be setup related. For your setup, I suggest using port 26 for TLS. That is what I am using on my live system. If that doesn’t work, check your email provider to see what they recommend for TLS settings on SMTP server.

    #2157
    StuartW
    Participant

    First a bit more background. We run our own mail server but there was nothing in the logs. The invoice site is protected first by basic Apache authentication (user and password) and secondly by a login with password to the invoicing site (along with other scripts that check the logs and adjust the firewall againat bad actors) The error reported stemmed from the webserver denying access to its own address in the absence of the server user/ password. Changing the apache server basic authentication to allow a curl request from itself. sufficed to allow the request to be actioned. It succeeded. Again many thanks for your prompt reply and hints.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.