Reply
Ubiquiti Employee
Posts: 2,323
Registered: ‎12-10-2015
Kudos: 839
Solutions: 208

New UCRM upgrades released: 2.10.1 and 2.11.0-beta2

Hi all,

new hotfix versions for stable and beta version have been released. Check the details below.

 

Use the in-app upgrade tool.

If you are running UCRM v. 2.6.0+ or 2.6.0-beta2+, use the in-app upgrade tool. Otherwise, use this guide to upgrade.

 

Feature requests

please add new one or upvote an existing one in  UCRM Feature Requests

 

Changelog

2.10.1

Added

  • Now, you can allow mail servers with self-signed certificate.

Fixed

  • Fixed pruning of old UCRM backup files.
  • Fixed UI responsivity for Ticketing section in the Client Zone.
  • Fixed permanent deleting of a client having a payment subscription.
  • Several minor fixes and improvements.

 

2.11.0-beta2

(includes also items mentioned in 2.10.1)

Added

  • Extensions for customizable templates. You can show billing period type (e.g. "backward", "forward") and show and modify dates (e.g. Invoice Due Date + 2 days).

Changed

  • Tickets based on blacklisted emails are pruned but tickets associated with clients are excluded from this pruning now.

Fixed

  • Fixed occasional image loading failures for invoices, login page, etc
  • Fixed UCRM upgrade failures in case Elastica failed to start.
Established Member
Posts: 1,851
Registered: ‎07-17-2009
Kudos: 188
Solutions: 4

Re: New UCRM upgrades released: 2.10.1 and 2.11.0-beta2

Does this include the code to show error messages for failed recurring subscriptions?

Ubiquiti Employee
Posts: 2,323
Registered: ‎12-10-2015
Kudos: 839
Solutions: 208

Re: New UCRM upgrades released: 2.10.1 and 2.11.0-beta2

yes, it does @avolve
New Member
Posts: 2
Registered: ‎03-16-2017

Re: New UCRM upgrades released: 2.10.1 and 2.11.0-beta2

Po dub 16 21:31:01 CEST 2018 --- Initializing UCRM update to version 2.11.0-beta2.
Po dub 16 21:31:01 CEST 2018 --- Downloading current updater.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 43526 100 43526 0 0 31362 0 0:00:01 0:00:01 --:--:-- 31358
Po dub 16 21:31:03 CEST 2018 --- Starting the update process.
+------------------------------------------------+
| UCRM - Complete WISP Management Platform |
| |
| https://ucrm.ubnt.com/ (updater v2.6) |
+------------------------------------------------+

Setting UPDATE_TO_VERSION=2.11.0-beta2
Setting CRON=true
Skipping auto-update permissions setup.
Backing up docker compose files.
Updating elastic service
Pulling rabbitmq (rabbitmq:3)...
3: Pulling from library/rabbitmq
Digest: sha256:443b95ecc1bb63797b0244452ba207cb5d1abf6530690ac98ebfc46a3bd79a2b
Status: Image is up to date for rabbitmq:3
Pulling postgresql (postgres:9.5)...
9.5: Pulling from library/postgres
Digest: sha256:888b62ebb1265a7df59258fa22227e707faa2b39d9abfe2a1d6f9e3cd5936468
Status: Image is up to date for postgres:9.5
Pulling elastic (docker.elastic.co/elasticsearch/elasticsearch-oss:6.2.2)...
6.2.2: Pulling from elasticsearch/elasticsearch-oss
Digest: sha256:2340904dc75d43373b6cc81935b43eda459dbabec83455f6cee6fd24269abe18
Status: Image is up to date for docker.elastic.co/elasticsearch/elasticsearch-oss:6.2.2
Pulling web_app (ubnt/ucrm-billing:2.11.0-beta2)...
2.11.0-beta2: Pulling from ubnt/ucrm-billing
error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/d4/d49565e915c5463b...: dial tcp: lookup dseasb33srnrn.cloudfront.net on 127.0.1.1:53: read udp 127.0.0.1:49001->127.0.1.1:53: i/o timeout
Image for version "2.11.0-beta2" not found.
Reverting docker compose files.
Po dub 16 21:31:34 CEST 2018 --- Update failed.

Ubiquiti Employee
Posts: 2,323
Registered: ‎12-10-2015
Kudos: 839
Solutions: 208

Re: New UCRM upgrades released: 2.10.1 and 2.11.0-beta2

@jasio14766
"Image for version "2.11.0-beta2" not found." indicates there was some temporary docker hub outage. Try the update again, should be fine.
Reply