Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,499,052
Community Members
 
Community Events
179
Community Groups

Email Confiig Error

I'm trying to config the Service Desk email but I always received an error message :

 

SOCKS: TTL Expired

5 answers

same here!

Plz explain u r issue

Why are there never simple answers to the many many many configuration challenges with Jira? Atlassian's products just keep getting more and more convoluted.

Alexandre Oliveira,

Did you ever get this issue resolved? I am having the same issue and was wondering what the resolution was for you.

 

Thanks

Exact Same issue here. Identical conditions and results. 

@monkeytronics can you send a test email through jira system and provide me the logs

Hi @Fahad Siddiqui , my maining problem it's inside IMAP email config inside Service Desk.

Projects -> Service Desk -> Config -> Email Setting

When I set the host and IMAPS : 993 I received this error message.

what protocol are you using? 

 

can you please share the screen shot of email settings

I tried IMAP / IMAPS / POP / POPS and I received the same error message.

but inside my system (writed in Java) I changed all parameters and it's working. And inside my email client too.

 

HOST: mail.chameleon.global

Like Fahad Siddiqui likes this

Good to know this your issue got fixed....

Please inform if anything else required from my side.

No, the email problem it's not working inside Jira

The problem still inside Jira config.

Are you able to ping the Ip address?

can you share the configuration page with screen shot

Yes! I used inside my email client without problem , bit inside jira service desk I can't connect on server

I tried to reconfigure and keep receiving the same error message "Socket Time out" and "SOCKS: TTL Expired", I think that Service Desk email config have a big problem to configure an external email.

config.png

This is my config options

@Alexandre Oliveira@Fahad Siddiqui  This is related to network issue, You need to contact your network team

Please go in Run command.

Type CMD

Then type: Ping -a mail.chameleon.global -t

Monitor the reply status... there will be request time out i believe as there is issue in network connection

@Fahad Siddiqui, I did it and it's working without problem

 

ping -a mail.chameleon.global -t

Pinging mail.chameleon.global [67.20.76.205] with 32 bytes of data:
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=201ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=200ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51
Reply from 67.20.76.205: bytes=32 time=199ms TTL=51

Ping statistics for 67.20.76.205:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 201ms, Average = 199ms
Control-C

Like Mikhail Iofik likes this

Got same error (SOCKS: TTL Expired)

Me too. 

I have verified the IMAP settings with other tools and our provider (Bluehost).  I see a couple of "SOCKS: TTL Expired" threads out there that just go silent.  Is there a fix?  Thanks!

Experiencing exact same issue now for no apparent reason. Network and mail server working fine with all other clients, only JIRA reporting this issue and we're unable to receive any incoming issues.

Same here! If someone knows how to fix this, please post. Migrating to cloud didn't help.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events