jgraeff
November 14, 2022, 11:00pm
1
Login page currently shows this instead:
HTTP Status 404 – Not Found
Type Status Report
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.75
I have restarted the VM, still same issue. Tried HTTP and HTTPS. Same 404 error.
Any ideas how to fix?
joer
November 15, 2022, 12:52am
2
we had the same issue this morning as well. A restart sorted it, but trying to work out what the issue was... interesting to find this post.
jgraeff
November 15, 2022, 2:01am
3
didn't fix it for me :( tried two reboots no luck.
Sorry to hear this,
Can you kindly confirm when this happens, is it occurring in your METL instance or when trying to use the Hub?
Kind regards, Joe
Bobec
August 13, 2024, 10:31am
5
Hi, I am getting this issue again, the restart of the VM did not solved it. Any idea what else can I do? Thank you!
joer
November 17, 2022, 10:57pm
6
Thanks for the reply Joe. Ours was the METL instance. The VM looked fine, and showed no issues... the METL Instance though was down with the 404 message mentioned above.
Hi @Bobec and I'm sorry to hear you've run into this issue again. If the restarts didn't work, can I suggest that you contact our support team if you've not already done so, so that they can investigate further.
Many thanks,
Claire
We are seeing this behavior today. Did you find a resolution?
A second restart of the VM solved the issue.
Sorry about that @MB094596
I have reached out internally regarding this, I will be back in contact once I hear back.
kind regards, Joe
Hi all,
Thank you all so much for your patience while we spoke to the team.
@MB094596 , I can see that a second restart solved the issue. Have you had any further issues since the restart?
Could I ask that for anyone still getting the 404, could you please open a support ticket so that the team can investigate further.
Many thanks,
Claire
Hello @ClaireSeniorCommunityManager , thank you for following up.
A second restart did solve the issue for us and we have not had any further issues since the second restart.
Regards,
Mike
Hi Mike / @MB094596 , thanks so much for confirming and I'm glad to hear that you've not had any further issues. If it does appear again though, please contact support so that the team can investigate further.
Thanks again!
Claire