nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira site can't be reached

Jero Dungog_dety91

I have an installation of Jira server on an ubuntu server.

This just happened today.
my monitor showed that Jira went down together with confluence.

So I went into the server and restarted it via the script on: /opt/atlassian/jira/bin/startup.sh
But it was returning:

This site can’t be reached

So I went to AWS and restarted the physical server itself. This however did not resolve my issue.

After I restarted the physical server and started jira both via startup.sh and start-jira scripts I still get the This site can't be reached error.

Can anyone help me with this issue?

Thank you!

Accepted answers

Fabio Racobaldo _Catworkx_

Hi @Jero Dungog ,

welcome to the Atlassian community.

Please could you share log file error? It should be located to JIRA_HOME/log

https://confluence.atlassian.com/jirakb/useful-log-files-in-jira-1027120387.html

We need this inf in order to figure out what happened.

Fabio

All comments

Fabio Racobaldo _Catworkx_

Hi @Jero Dungog ,

welcome to the Atlassian community.

Please could you share log file error? It should be located to JIRA_HOME/log

https://confluence.atlassian.com/jirakb/useful-log-files-in-jira-1027120387.html

We need this inf in order to figure out what happened.

Fabio

Jero Dungog_dety91

Thank you for responding @Fabio Racobaldo _Catworkx_
Below is the latest log entry after I restarted Jira:

2022-03-02 18:39:10,959 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

***********************************************************************************
JIRA 8.2.5 build: 802005 started. You can now access JIRA through your web browser.
***********************************************************************************

2022-03-02 18:39:10,983 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system lateStartup begun
2022-03-02 18:39:10,987 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system lateStartup ended
2022-03-02 18:39:10,989 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.atlassian-whitelist-core-plugin]
2022-03-02 18:39:11,023 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Plugin System Started _________________

2022-03-02 18:39:11,091 JIRA-Bootstrap INFO [c.a.jira.upgrade.UpgradeScheduler] Scheduling upgrades to run in 1 minute(s)
2022-03-02 18:39:12,143 JIRA-Bootstrap INFO [c.a.j.c.embedded.ofbiz.IndexedUserDao] Reindex all users took: 1.038 s
2022-03-02 18:39:12,218 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [pl.com.tt.jira.plugin.theschedulerpro]
2022-03-02 18:39:14,069 JIRA-Bootstrap WARN [c.c.j.p.automation.schedule.RulePollerServiceLauncher] Scheduling automation rule poller job
2022-03-02 18:39:14,076 JIRA-Bootstrap WARN [c.c.j.p.automation.schedule.RulePollerServiceLauncher] Success scheduling automation rule poller job
2022-03-02 18:39:14,085 WaitForAO DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.jira.plugins.jira-dvcs-connector-plugin]
2022-03-02 18:39:14,095 JIRA-Bootstrap WARN [c.c.j.p.automation.schedule.RuleScheduleServiceLauncher] Scheduling automation rule scheduler job
2022-03-02 18:39:14,101 JIRA-Bootstrap WARN [c.c.j.p.automation.schedule.RuleScheduleServiceLauncher] Success automation rule scheduler job
2022-03-02 18:39:17,136 JIRA-Bootstrap INFO [c.a.j.config.managedconfiguration.DefaultManagedConfigurationItemStore] Managed Configuration Item registered: com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItem@617af9ee[id=10200,itemId=customfield_10600,itemType=CUSTOM_FIELD,isManaged=true,configurationItemAccessLevel=LOCKED,sourceId=<null>,descriptionI18nKey=admin.managed.configuration.items.generic.description.locked]
2022-03-02 18:39:17,218 Modification Check:thread-1 INFO [c.a.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties
Removed Files : None

2022-03-02 18:39:19,744 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.jira.plugin.automation.for-jira]
2022-03-02 18:39:20,027 JIRA-Bootstrap WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Initialising automation-rule-executor pool with 6 threads...
2022-03-02 18:39:20,028 JIRA-Bootstrap WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] automation-rule-executor pool running with 6 threads.
2022-03-02 18:39:20,028 JIRA-Bootstrap WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Initialising automation-queue-claimer...
2022-03-02 18:39:20,031 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] automation-queue-claimer is running.
2022-03-02 18:39:20,031 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] JQL search indexes are currently not available (Indexing: true, Scheduler: STANDBY). No automation items were claimed from the queue for processing on this node since most automation rules depend on JQL indexes being available.
2022-03-02 18:39:20,040 JIRA-Bootstrap INFO [c.a.j.p.e.bamboo.service.PlanStatusUpdateServiceImpl] PlanStatusUpdateJob scheduled to run every 60 seconds
2022-03-02 18:39:20,094 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.labs.hipchat.hipchat-for-jira-plugin]
2022-03-02 18:39:20,095 JIRA-Bootstrap INFO [c.a.j.p.hipchat.service.HipChatPluginLauncher] Hipchat Plugin launched successfully
2022-03-02 18:39:20,095 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.event.PluginStartedEvent
2022-03-02 18:39:20,099 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] Registering a new hipchatRefreshConnectionStatusJob task.
2022-03-02 18:39:20,106 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.event.PluginStartedEvent
2022-03-02 18:39:20,108 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] Registering a new hipchatUpdateGlancesDataJob task.
2022-03-02 18:39:20,112 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.event.PluginStartedEvent
2022-03-02 18:39:20,113 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.AbstractTaskScheduler] Registering a new hipchatInstallGlancesJob task.
2022-03-02 18:39:23,213 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.pyxis.greenhopper.jira]
2022-03-02 18:39:23,339 JIRA-Bootstrap WARN [c.o.s.runner.startup.JiraStartupManager] Waiting for jql functions registration
2022-03-02 18:39:23,340 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler....
2022-03-02 18:39:23,368 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler started.
2022-03-02 18:39:23,425 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 512 MiB. Committed: 1974 MiB. Max: 1988 MiB
Non-heap memory : Used: 341 MiB. Committed: 369 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 853 MiB. Committed: 2343 MiB. Max: 3524 MiB
---------------------------------------------------------------------------------
2022-03-02 18:39:29,533 Caesium-1-1 WARN ServiceRunner [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '26cde378-fce6-3911-87d8-7ff208ce8c3f'
2022-03-02 18:39:29,534 Caesium-1-2 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [doitbetter.calendar]
2022-03-02 18:39:29,566 Caesium-1-1 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Running start-index-recovery
2022-03-02 18:39:29,643 Caesium-1-2 INFO ServiceRunner [c.a.jira.startup.CacheWarmerLauncher] Warming up 3 caches.
2022-03-02 18:39:29,647 ForkJoinPool.commonPool-worker-2 INFO ServiceRunner [c.a.jira.i18n.I18nWarmer] Init i18n cache
2022-03-02 18:39:29,648 ForkJoinPool.commonPool-worker-1 INFO ServiceRunner [c.a.j.cache.soy.SoyCacheWarmer] Warming 41 soy modules
2022-03-02 18:39:29,928 Caesium-1-1 INFO ServiceRunner [c.a.j.index.ha.DefaultIndexRecoveryManager] Latest index date: {2022-03-02 17:31:00}, Latest DB date: {2022-03-02 17:31:00}
2022-03-02 18:39:29,929 Caesium-1-1 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Indexing issues from=2022-03-02 17:31:00.0 to=Wed Mar 02 17:31:00 UTC 2022 (time span of 0ms)
2022-03-02 18:39:29,930 Caesium-1-1 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=60%, task=Recovering, message=Recovered added and updated issues
2022-03-02 18:39:30,061 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,074 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,075 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,075 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,075 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,075 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,075 Caesium-1-1 WARN ServiceRunner [c.a.jira.ofbiz.IssueGenericValue] Issue (id=0) has empty field 'num'. Returning null for 'key'.
2022-03-02 18:39:30,076 Caesium-1-1 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Progress=80%, task=Recovering, message=Cleaned removed issues
2022-03-02 18:39:30,076 Caesium-1-1 INFO ServiceRunner [c.a.jira.startup.IndexRecoveryLauncher] Finished start-index-recovery
2022-03-02 18:39:30,084 Caesium-1-3 ERROR ServiceRunner [c.a.s.caesium.impl.SchedulerQueueWorker] Unhandled exception thrown by job QueuedJob[jobId=JiraPluginScheduler:com.atlassian.analytics.client.upload.RemoteFilterRead:job,deadline=1646246364081]
javax.xml.stream.FactoryConfigurationError: Provider for class javax.xml.stream.XMLInputFactory cannot be created
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:370)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:313)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:227)
at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:154)
at com.amazonaws.util.XmlUtils.createXmlInputFactory(XmlUtils.java:62)
at com.amazonaws.util.XmlUtils.access$000(XmlUtils.java:27)
at com.amazonaws.util.XmlUtils$1.initialValue(XmlUtils.java:35)
at com.amazonaws.util.XmlUtils$1.initialValue(XmlUtils.java:32)
at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180)
at java.lang.ThreadLocal.get(ThreadLocal.java:170)
at com.amazonaws.util.XmlUtils.getXmlInputFactory(XmlUtils.java:53)
at com.amazonaws.services.s3.internal.S3ErrorResponseHandler.createException(S3ErrorResponseHandler.java:93)
at com.amazonaws.services.s3.internal.S3ErrorResponseHandler.handle(S3ErrorResponseHandler.java:64)
at com.amazonaws.services.s3.internal.S3ErrorResponseHandler.handle(S3ErrorResponseHandler.java:51)
at com.amazonaws.http.AwsErrorResponseHandler.handleAse(AwsErrorResponseHandler.java:50)
at com.amazonaws.http.AwsErrorResponseHandler.handle(AwsErrorResponseHandler.java:38)
at com.amazonaws.http.AwsErrorResponseHandler.handle(AwsErrorResponseHandler.java:24)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1612)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1302)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1056)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699)
at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667)
at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4365)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4312)
at com.amazonaws.services.s3.AmazonS3Client.getObject(AmazonS3Client.java:1415)
at com.amazonaws.services.s3.AmazonS3Client.getObject(AmazonS3Client.java:1276)
at com.atlassian.analytics.client.s3.AnalyticsS3Client.getS3ObjectInputStream(AnalyticsS3Client.java:106)
at com.atlassian.analytics.client.eventfilter.reader.RemoteListReader.getRemoteListObject(RemoteListReader.java:29)
at com.atlassian.analytics.client.eventfilter.reader.RemoteListReader.readFilterList(RemoteListReader.java:25)
at com.atlassian.analytics.client.eventfilter.parser.SimpleListParser.readSimpleFilterList(SimpleListParser.java:47)
at com.atlassian.analytics.client.eventfilter.BlacklistFilter.readBlacklist(BlacklistFilter.java:54)
at com.atlassian.analytics.client.eventfilter.BlacklistFilter.readRemoteList(BlacklistFilter.java:46)
at com.atlassian.analytics.client.upload.RemoteFilterRead.execute(RemoteFilterRead.java:52)
at com.atlassian.scheduler.compat.local.LocalOnlyPluginJob.execute(LocalOnlyPluginJob.java:30)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:110)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:80)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:435)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:402)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:380)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Provider for class javax.xml.stream.XMLInputFactory cannot be created
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:367)
... 49 more
Caused by: java.util.ServiceConfigurationError: javax.xml.stream.XMLInputFactory: Provider com.ctc.wstx.stax.WstxInputFactory not found
at java.util.ServiceLoader.fail(ServiceLoader.java:239)
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at javax.xml.stream.FactoryFinder$1.run(FactoryFinder.java:353)
at java.security.AccessController.doPrivileged(Native Method)
at javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:341)
... 49 more
2022-03-02 18:39:31,603 ForkJoinPool.commonPool-worker-1 INFO ServiceRunner [c.a.j.cache.soy.SoyCacheWarmer] Warmed 41 soy module(s) in 1956 ms, 0 module(s) were not present or disabled, 0 failed.
2022-03-02 18:39:37,122 Caesium-1-4 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.base-hipchat-integration-plugin-api]
2022-03-02 18:39:38,908 ForkJoinPool.commonPool-worker-2 INFO ServiceRunner [c.a.jira.i18n.I18nWarmer] Initialised i18n cache in 9260
2022-03-02 18:39:38,908 Caesium-1-2 INFO ServiceRunner [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 9264 ms.
2022-03-02 18:39:42,352 Caesium-1-4 INFO ServiceRunner [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2022-03-02 18:39:48,787 Caesium-1-4 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
2022-03-02 18:39:48,787 Caesium-1-4 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to Hipchat, no need to install glances.
2022-03-02 18:40:11,095 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-03-02 18:40:11,104 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-03-02 18:40:11,350 Caesium-1-4 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 802005
2022-03-02 18:40:11,356 Caesium-1-4 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin]
2022-03-02 18:40:11,390 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-03-02 18:40:11,390 Caesium-1-4 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.2.5
2022-03-02 18:40:11,399 Caesium-1-4 INFO ServiceRunner [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-03-02 18:40:11,411 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 307 milliseconds to process.
2022-03-02 18:40:11,411 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-03-02 18:40:11,415 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-03-02 18:40:11,416 Caesium-1-4 INFO ServiceRunner [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests
2022-03-02 18:40:14,301 HealthCheck:thread-8 WARN ServiceRunner [c.a.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link '26cde378-fce6-3911-87d8-7ff208ce8c3f'
2022-03-02 18:40:17,198 Caesium-1-1 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.troubleshooting.plugin-jira]
2022-03-02 18:41:07,944 Timer-4 WARN [r.t.j.p.subscriptions.listen.SubscrListener] Add service Subscription Find Duplicates Filters, 0 0 1 * * ?
2022-03-02 18:44:08,321 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [plugin-transaction] numberStartEvents:223, numberEndEvents:223, numberSendEvents:223, numberEventsInTransactions:454, numberOfPluginEnableEvents:0
2022-03-02 18:49:08,321 plugin-transaction-0 INFO [c.a.jira.plugin.PluginTransactionListener] [plugin-transaction] numberStartEvents:223, numberEndEvents:223, numberSendEvents:223, numberEventsInTransactions:454, numberOfPluginEnableEvents:0

Jero Dungog_dety91

@Fabio Racobaldo _Catworkx_

This was working fine earlier and just today it became like this.
Other info which might be helpful:
I have two applications running on the same server machine: Jira (8080) and Confluence (8090)
I am using nginx to handle them.

Sachin Dhamale_o1c5zi

@Jero Dungog ,

Can you Clear the Plugin Cache and Try to restart Jira again

Stop the JIRA instance
Delete JIRA_HOME/plugins/.bundled-plugins and JIRA_HOME/plugins/.osgi-plugins (" data-emoji-fallback="" data-emoticon-name="warning" /> just these two folders!)
Restart JIRA

Accept the answer if its help

Fabio Racobaldo _Catworkx_

Did u try to reach jira and confluence directly without use nginix?

http://YOUR_SERVER_IP:8080/

if you setup a context within server.xml file add it to url.

Please try and let me know.

Fabio

Fabio Racobaldo _Catworkx_

@Sachin Dhamale , @Jero Dungog had problem on both JIRA and Confluence at the same time so it should be not related to plugins cache.

Sachin Dhamale_o1c5zi

@Jero Dungog ,

Can you try to access jira on the jira server itself? just to confirm jira is accessible on same server if yes then it will be some network issue or port something similar

Jero Dungog_dety91

@Sachin Dhamale do you mean using curl?

Jero Dungog_dety91

@Fabio Racobaldo _Catworkx_ & @Sachin Dhamale
Thank you both for your time and effort in helping me out with regards to this issue.

Fabio was right, this was a configuration issue.

What I found out was that the NGINX config was ok, it was instead my ec2 instance being blocked by AWS from performing any outside calls.

This was due to a malware which had infected the server and was making significant number of calls to foreign ip addresses. Which AWS flagged as a DDOS attack and thus blocked my ec2 instance.

Again, thank you so much to the both of you for helping me out!
I really appreciate it.

Best regards,
Jero

Fabio Racobaldo _Catworkx_

thanks @Jero Dungog for your feedback. Please mark my answer as accepted!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server