02-23-2018 05:24 AM
a new hotfix release is out. Check the details below.
If you are running UCRM v. 2.6.0-beta2+, use the in-app upgrade tool.
If you are on 2.10.0-beta2 and can't log in, or if you are running version without in-app upgrade tool, use this guide to upgrade.
please add new one or upvote an existing one in UCRM Feature Requests
- Fixed localization issue preventing login after update to 2.10.0-beta2.
- Fixed problem in FCC report generation.
- Fixed address not pre-filled, when new job is created from client's detail page.
- Fixed NetFlow charts not visible in admin zone in some cases, when there are data available.
- Minor UI fixes.
- Improved design of the client log.
- Improvements to Service Device API. Now it's possible to edit service device and delete service IPs.
- Czech localization added.
- Custom SSL certificate can be now used with IP address only (with no server domain defined in system settings). Server domain remains required for Let's Encrypt. Also, when server IP / domain is changed, the server configuration is regenerated automatically (no need to re-upload the certificates or restart UCRM).
- Creating a canned ticketing response failing when longer text was used.
- Client count is no longer displayed on dashboard for users without view permission for clients.
- Fixed permission error with canned responses in Client Zone Support section.
- Minor UI/UX fixes.
02-25-2018 01:46 PM
IMAP Import to ticket seems broken with some email service providers. It works fine on imap.gmail.com with our general gmail adress. But our Tech/Support address with our domain providers doesnt work with the correct imap settings.
We know for sure that the IMAP import if working with our domain provider because we are currently importing all Tech and Support email our our general email.
02-26-2018 12:52 AM
Hello @saburgei, currently all ticket related email notifications going to admin users are sent to the "Support email address", that is configured in System -> Settings -> Mailer.
We are preparing improvement for this, which will enable you to choose the target for every notification in UCRM, including configuration to send to all admin users.
02-26-2018 10:42 AM
When I click the connection test i receaive a positive feedback that everything is working. However no tickets are generated from the email inbox.
More explanation : We have a domain name with our service provider example ; Domain.com. We also have a couple of email associated with that domain name : Tech@Domain.com Support@Domain.com etc.
We also have a generic Gmail address OurCompany@gmail.com. We currently use Gmail imap import for our XYZ@Domain.com to manage everything from the Gmail portal.
We successfully created tickets with Imap Import tool in UCRM with our OurCompany@gmail.com. Now with want to do the same with our Support@Domain.com. Unfortunately it seems to ne be working with custom email address from service providers. When we test the connection with the Support@Domain.com everything is "Ok'ed".
Note : We use the same TLS/non TLS certificated from gmail and ports for our @domain.com addresses.
02-27-2018 07:34 AM
@kruse1944 Thank you for your report! But I am not able reproduce this issue. But I have idea. UCRM does not imports emails from "UCRM itself" (e.g. sender email or oganisation email address) so please check that this not this case.
03-03-2018 09:09 AM
Well, HTTPS service did not start after the upgrade, and after a restart it came back up and is sort of stable. The displayed version is still 2.9.0-beta3 but it would not let me upgrade to 2.9.2 because it says it is already upgraded to 2.10.0-beta3
Update from "2.10.0-beta3" to "2.9.2" is not possible. You can only update to newer version.
Fri Feb 23 23:03:05 GMT 2018 --- Update failed.
Will try again once a new release is coming out.
03-05-2018 12:19 AM
Hello @justmeccsn, I still don't get what you mean by HTTPS service not starting. Did your UCRM run fine but only on HTTP, or did it not run at all?
How did you reverted back to 2.9.0-beta3? If you run "sudo docker logs ucrm_web_app_1", do you see any errors?
03-05-2018 12:28 AM
@justmeccsn Also, could you please post a screenshot of the in-app update screen in UCRM and contents of your docker-compose.yml file? You can find the yml at /home/ucrm.
03-05-2018 01:23 PM
Update on the issue. I might have found the issue yesterday. It does sync customs domain name emails but at a really really low sync rate. I've tested 10 "support emails" and the average UCRM integration was around 15 minutes. It might be a UCRM limitation to sync faster incoming emails.
However while doing theses tests I've found a pretty funny looped bug. We've setup'd our domain provider billing adress to that Support@domain.com. When UCRM receive that receipt it does his job and create a Ticket. The funny part is it sends an auto aknowledge email for the ticket receival to the domain provider accounding email. And the accounting email replies back with a auto akwoledge itself and on and on it creates a infinite loop of Auto respond andtickets between 2 computers.
This made me think it might be a great idea to integrate a "exclude email list" for tickets and billing.
03-05-2018 01:35 PM
When i initially upgraded, opening the CRM via the browser timed out. Looking on the VM where UCRM was running it appeared that the HTTP service was not running after the upgrade. My colleague then restarted the VM which made it work.
I ran another upgrade a couple of days ago and all is good now, everything works as it should. No need to try and help me as it works. Probably something I did that caused it .
Many thanks guys for your awesome support!
03-05-2018 03:25 PM
I am noticing after this update that the QoS standards based on the packages I have set up are no longer being pushed or enforced on my edgerouter. I am currently using the Edge Router Infinity with the latest stable firmware. I am hosting my UCRM in the cloud and pushing all commands to the router public static IP address. QoS schedular in router is empty. No QoS rules are in place anymore.
03-05-2018 07:50 PM
@dr-lea please check the router log for any errors, and send us some screen with details: Network > Devices > chose the router where the QoS is synchronized