[RTFACT-21709] Artifactory Tomcat UI started returning 404 errors Created: 06/Apr/20  Updated: 06/Jan/21

Status: Open
Project: Artifactory Binary Repository
Component/s: Web UI
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Aitzol CASADO Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None

Severity: Medium

 Description   

Hello,

Our Artifactory UI has been down for a while (The back end and repository appear to work as normal).

If we attempt to hit the web root or /UI we get the following Apache tomcat error rather than the expected login screen:

 

HTTP Status 404 - Not Found
Type Status Report
Message /ui/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Nothing is logged to <artifactory-home>/log/tomcat/tomcat-localhost* or <artifactory-home>/log/tomcat/tomcat-catalina* when we attempt to hit the UI.

 

Any pointers to relevant logs would be appreciated?

I note that the following folder in our install is currently empty:

<artifactory-home>/etc/artifactory/ui

Kind regards,

Aitzol CASADO



 Comments   
Comment by Georg Abenthung [ 09/May/20 ]

Same problem here. I'm using the official Docker image for running our instance of Artifactory OSS (Docker image: docker.bintray.io/jfrog/artifactory-oss:latest).
When I'm calling on of the following URL'S

https://arti.example.com/
https://arti.example.com/artifactory/

I'm getting redirected to https://arti.example.com/ui/

which throws an 404  error. (Tomcat error-page is shown).

 

@Aitzol CASADO: Have you already found a solution for this problem?

 

Comment by Aitzol CASADO [ 12/May/20 ]

Hi @Georg Abenthung,
Apologies that I cannot remember the full details, but in our case, the issue was related to the port on which tomcat (that used/managed by Artifactory) was starting up. We had theoretically configured it to boot up on port 8081, but for some reason, that port was showing up as occupied and either tomcat or some related startup code from Artifactory was attempting to be too smart and thus choosing port 8082. I can't remember the configuration changes we ended up doing to fix this, but I would suggest starting to diagnose this by looking at the ports being used by tomcat on your server. 
Once you think you know what port the Artifactory UI is running on, you should be able to then test it locally via links/elinks or similar (http://localhost:8081) before having to deal with any reverse proxy or port forwarding configuration to the outside world.

Comment by Georg Abenthung [ 20/May/20 ]

Hello, thanks @Aitzol CASADO .

It seems artifactory changed some configuration recently. I had to update our Apache Webserver's Proxy settings:

https://www.jfrog.com/confluence/display/JFROG/Configuring+Apache

 

Generated at Wed Apr 14 20:09:57 UTC 2021 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.