Installation Successful, Browser Times Out
Asked by donniebrandt:

**Problem**

I successfully installed atlassian-confluence-6.7.1-x64.bin package and it says that I can access it at http://localhost:8090. The request times out, however, the host is fine.

It appears that the package is bundled with all required software (<https://confluence.atlassian.com/doc/system-requirements-126517514.html>).

**Environment**

- DigitalOcean

- Ubuntu 16.04.4

- MySQL 14.14

- tcp6 0 0 :::8090 :::\* LISTEN -


Answers:
author: Shannon S
body: Hi Donnie,

Do you have any error messages you can share with us? You can check the [Confluence server logs](https://confluence.atlassian.com/doc/working-with-confluence-logs-108364721.html).

Can you confirm that you haven't run the setup yet? Is this after the first startup?

Regards,

Shannon

comments: author: donniebrandt
body: Hey Shannon,

To confirm, I have not run the setup yet, simply the install process. Here is the entire log (pretty short).

```
2018-02-27 21:25:49,179 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.7.1 [build 7601 based on commit hash d9a7d86ddd6172b1b5a38b9e600c8b90c362def3] - synchrony version 2.1.0-release-confluence_6.5-1a01ab2d2018-02-27 21:26:07,936 WARN [localhost-startStop-1] [com.atlassian.config.ApplicationConfig] setApplicationHome Application home does not exist. Creating directory: /var/atlassian/application-data/confluence/shared-home2018-02-27 21:26:07,962 INFO [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...2018-02-27 21:26:07,966 WARN [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Could not find shared config file.2018-02-27 21:26:12,684 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] earlyStartup Plugin system earlyStartup begun2018-02-27 21:26:21,106 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system earlyStartup ended2018-02-27 21:26:21,117 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] lateStartup Plugin system lateStartup begun2018-02-27 21:26:23,584 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system lateStartup ended2018-02-27 21:26:26,361 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
```


author: Shannon S
body: Hi Donnie,

Thank you for confirming. So it seems the issue is not with Confluence but the server itself.

I'm not familiar with DigitalOcean myself, but generally, you can test it like so:

1. Accessing directly via IP address:8090
2. Try curl localhost 8090

Also, I want to note, that you mentioned you're using MySQL 14.14. The latest stable release is 5.7.21, so can you please confirm your MySQL version? I want to be sure that you're using a proper version for [Confluence's supported platforms](https://confluence.atlassian.com/doc/supported-platforms-207488198.html) to ensure you don't run into further issues in the future.

Regards,

Shannon


author: donniebrandt
body: I'm having no luck accessing it via the direct IP address or through curl.

Apologies on the incorrect MySQL version. It is indeed 5.7.21.


author: Shannon S
body: Thank you for confirming Donnie.

You may need to talk to DigitalOcean to see what is missing here. Were you already able to access other sites on your droplet in this same manner?

What is the exact timeout screen you get? Is there anything in catalina.out?

Regards,

Shannon


author: donniebrandt
body: This is a sample of what I see in catalina.out:

```
01-Apr-2018 21:44:43.651 INFO [http-nio-8090-exec-2] org.apache.coyote.http11.AbstractHttp11Processor.process Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens        at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:235)        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1045)        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1539)        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1495)        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)        at java.lang.Thread.run(Thread.java:748)
```


author: Shannon S
body: Donnie,

Is there anything else in that log? The message you sent is purely informational, so if you see any error messages please let me know, as well as any lines that mention "caused by" after the error messages.

As for that message, I found [a post on the Docker forum](https://forums.docker.com/t/confluence-invalid-character-found-in-method-name/28276) (understood you're not using Docker but maybe it will help) mentions it means you don't have https enabled.

Regards,

Shannon


author: donniebrandt
body: Thanks, Shannon.

I enabled HTTPS but that has not helped.

I don't see errors in catalina.out. The INFO message above is one that repeats over and over. However, I do have these warnings from early in the log if they help:

```
27-Feb-2018 21:25:39.938 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
27-Feb-2018 21:25:40.166 WARNING [main] org.apache.catalina.startup.SetAllPropertiesRule.begin [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.
27-Feb-2018 21:25:40.194 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
27-Feb-2018 21:25:40.209 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.
27-Feb-2018 21:25:40.317 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
27-Feb-2018 21:25:40.394 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
2018-02-27 21:26:07,936 WARN [localhost-startStop-1] [com.atlassian.config.ApplicationConfig] setApplicationHome Application home does not exist. Creating directory: /var/atlassian/application-data/confluence/shared-home
2018-02-27 21:26:07,966 WARN [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Could not find shared config file.
```


author: Shannon S
body: Donnie,

Nothing from the logs seem to be error messages. I looked into it and a lot of these messages can often be seen on a working Confluence instance. In addition, you received the **Confluence is Ready to Serve** message which generally means there were no issues.

Since you're not able to curl to the IP:8090 after ssh-ing to the server makes me think there's either something wrong with the server or perhaps the way that you're attempting to access the page.

I would recommend reaching out to DigitalOcean and see what they say about this. Perhaps there's some other URL you need to use to access to get around a possible firewall.

When you do find out please let us know here, because it will help future users who try to set up with DigitalOcean.

Shannon