@PACKAGE_NAME@ @PACKAGE_VERSION@
The PHAR extension is available, but was unable to read this PHAR file's hash.
Regardless, you should not be having any trouble using the package by directly
including the archive.

Exception details:UnexpectedValueException: Cannot create phar '/var/www/html/app2/cron/Net_RouterOS/vendor/pear2/net_transmitter/stub.php', file extension (or combination) not recognised or the directory does not exist in /var/www/html/app2/cron/Net_RouterOS/vendor/pear2/net_transmitter/stub.php:36
Stack trace:
#0 /var/www/html/app2/cron/Net_RouterOS/vendor/pear2/net_transmitter/stub.php(36): Phar->__construct()
#1 {main}

================================================================================
The OpenSSL extension is loaded. If you can make any connection whatsoever, you
could also make an encrypted one.

Note that due to known issues with PHP itself, encrypted connections may be
unstable (as in "sometimes disconnect suddenly" or "sometimes hang when calling
TcpClient::isDataAwaiting() without a timeout").

================================================================================
The stream_socket_client() function is enabled.
If you can't connect to a host, this means one of the following:

1. You've mistyped the IP and/or port.
   Check the IP and port you've specified are the ones you intended.

2. The host is not reachable from your web server.
   Try to reach the host (!!!)from the web server(!!!) by other means
   (e.g. ping) using the same IP, and if you're unable to reach it,
   check the network settings on your web server, the remote host
   (if it's under your control) as well as any intermidiate nodes under your
   control that may affect the connection (e.g. routers, etc.).

3. Your web server is configured to forbid that outgoing connection.
   If you're the web server administrator, check your firewall's settings.
   If you're on a hosting plan... Typically, shared hosts block all
   outgoing connections, but it's also possible that only connections
   to that port are blocked. If the remote host is under your control,
   try to connect to it on a popular port (21, 80, 443, etc.),
   and if successful, keep using that port instead. If the connection fails
   even then, or if the remote host is not under your control, ask your host to
   configure their firewall so as to allow you to make outgoing connections
   to the ip:port you need to connect to.