Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why I can't access Jira when My IP is in the whitelisted

Esgi Dendyanri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 26, 2026

the company I work with has strict access based on IP, but I still dynamic IP which means my client need to put my IP each day on the whitelist. it's a pain to put it everyday so I contact my internet provider to get static IP as service, I get this IP 158.140.183.161

it detect correctly in this site and several IP detector site:

Screenshot 2026-03-26 170112.png

 

my client has input my IP on the whitelist:

image (62).png

but I always get 403 while accessing it, it's like atlassian can't detect my new static IP but could detect my dynamic one.

Screenshot 2026-03-26 170948.png

Request ID: 12bbec9cb9ae414596e3ab7f6ce0bc5f

what should we do about it?

1 answer

2 votes
Marc -Devoteam-
Community Champion
March 26, 2026

Hi @Esgi Dendyanri 

Welcome to the community 403 is a forbidden message.

So you or you company should trace where you are actually coming from.

You could do a trace route from your device to https://<name>.atlassian.net, see what the outcome is.

Did the Atlassian admin, press "save" to store the change made? 

Esgi Dendyanri
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 26, 2026

Hi  

thanks for the response, we sure have press "save"

this is the trace route that I did,

> tracert futurebright.atlassian.net

Tracing route to futurebright.atlassian.net [13.227.180.4]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.0.1
2 6 ms 3 ms 3 ms host-158.140.183-1.myrepublic.co.id [158.140.183.1]
3 * 6 ms * host-103-130-18-66.myrepublic.co.id [103.130.18.66]
4 7 ms 4 ms 5 ms host-103-130-18-65.myrepublic.co.id [103.130.18.65]
5 5 ms 4 ms 6 ms 103.47.134.246
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 4 ms 4 ms 4 ms server-13-227-180-4.kix82.r.cloudfront.net [13.227.180.4]

Trace complete.


not sure what Atlassian detect my IP is,

can you at least check with someone about my request id 12bbec9cb9ae414596e3ab7f6ce0bc5f?

like what actual IP that it detect, because this problem persist for several weeks, we also have try successfully with our Cloudflare server to allow my IP, so far Jira is the only one that I can't access

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events