web-pal / chronos-timetracker

Desktop client for JIRA. Track time, upload worklogs without a hassle.
https://chronos.web-pal.com
MIT License
298 stars 66 forks source link

Chronos 3.2.6 login issue #184

Closed dmkk3r closed 1 year ago

dmkk3r commented 5 years ago

Expected Behavior

Chronos should log user in.

Actual Behavior

Chronos stays at login mask with loader.

Steps to Reproduce the Problem

  1. Start Chronos.
  2. Input Jira Domain.
  3. Input user cred.

Specifications

Amr1977 commented 5 years ago

Same issue for me.

VladimirPal commented 5 years ago

@Amr1977 @dmkk3r Make sure you use the latest 3.2.6 version. Try to install it again https://github.com/web-pal/chronos-timetracker/releases

What type of authentication are you using? Login/Password or google? Cloud or Server jira?

dmkk3r commented 5 years ago

Iam on the latest version. Same problem after reinstall. Login via password on local jira server.

VladimirPal commented 5 years ago

@dmkk3r What's you jira server version? Can't reproduce it on my local server. Could you also try old chronos versions for test

VladimirPal commented 5 years ago

@Amr1977 What is your OS? Windows 10?

Amr1977 commented 5 years ago

@VladimirPal MacOS 10.14, I tried older versions 3.2.3/3.2.5 , didn't work

dmkk3r commented 5 years ago

OS: Windows 10 Jira server: 7.13.1

VladimirPal commented 5 years ago

@Amr1977 Cloud or Server?

dmkk3r commented 5 years ago

I have tested versions 3.2.6, 3.2 and 3.1, none of them has logged in. Is there a way to view the error message? Logs or open the Developer Console?

ivanyankov commented 5 years ago

Hi team, I have the same issue.

macOS High Sierra - version 10.13.6

I am using the latest version 3.2.6.

Amr1977 commented 5 years ago

@VladimirPal Turned to be my firewall settings, (everyone also make sure to use correct domain spelling)

dmkk3r commented 5 years ago

I have adjusted the firewall settings, but chronos still can not connect.

Could it be that chronos can not cope with the company proxy?

Amr1977 commented 5 years ago

@dmkk3r Try using VPN, if you could login then you still have to adjust more options in firewall.

VladimirPal commented 5 years ago

@dmkk3r @ivanyankov Do you use any system proxy?

dmkk3r commented 5 years ago

The problem was that the Jira server was equipped with a self-signed certificate and access was only forwarded via http. I manually referenced the server via http and it worked.