"There was an error communicating with the server: request timed out."

1,077 views
Skip to first unread message

elrobto sohn

unread,
Aug 20, 2018, 8:50:20 AM8/20/18
to Nexus Users
Hello,

How can i fix it?

Best Regards
support-20180820-141952-1.zip

Rich Seddon

unread,
Aug 20, 2018, 12:00:50 PM8/20/18
to Nexus Users
The slowest response time in the whole request.log is just over 2 seconds:

217.80.72.228 - - [20/Aug/2018:13:53:21 +0200] "GET /static/ext-3.4.1.1/ext-all.js HTTP/1.1" 200 719927 2136

The response time is in the last column, in milliseconds.

Wherever you are getting this timeout it is safe to assume the request is never even reaching Nexus.  It looks like you've got a network issue to debug.

Junio Souz

unread,
Sep 24, 2018, 1:07:15 PM9/24/18
to Nexus Users, elrobt...@gmail.com
In my case, I've disabled "Force Base URL" at Server Administration.

I configured a base url (by server name) and was acessing it by IP. That's the reason why the message were displayed to me and how I solved this problem.

No logs were printed on log files.

Rich Seddon

unread,
Sep 24, 2018, 1:51:40 PM9/24/18
to Nexus Users, elrobt...@gmail.com

FWIW, force base URL is not recommended, and should never be needed if your inbound network is configured correctly.

Reply all
Reply to author
Forward
0 new messages