Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-19616

Exception Can't convert custom provisioning address '' into a valid URL. This must be in the format of protocol://host:port - Please re-enter

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: Verion 2.2.5
    • Fix Version/s: None
    • Component/s: Asterisk Configuration
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      "Apache/2.4.6 (Sangoma) OpenSSL/1.0.1e-fips PHP/5.6.31"
    • Distro Version:
      sangoma pbxact 60

      Description

      Exception thrown with message "Can't convert custom provisioning address '' into a valid URL. This must be in the format of protocol://host:port - Please re-enter"

      Stacktrace:
      #4 Exception in /var/www/html/admin/modules/endpoint/functions.inc/functions_common.php:2369
      #3 endpoint_configVariables in /var/www/html/admin/modules/endpoint/functions.inc/functions_common.php:47
      #2 endpoint_write_ext in /var/www/html/admin/modules/endpoint/functions.inc.php:116
      #1 endpoint_configpageinit in /var/www/html/admin/libraries/BMO/GuiHooks.class.php:267
      #0 FreePBX\GuiHooks:doConfigPageInits in /var/www/html/admin/config.php:417

       

      Please Help! Bootet not more!
      "Can't convert custom provisioning address '' into a valid URL. This must be in the format of protocol://host:port - Please re-enter"

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kgupta Kapil Gupta
                Reporter:
                peterskyk peterskyk
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.