If this is on Linux: * The content of /etc/hosts would be interesting. * The output of ss -tulpn would be interesting.
You should make sure that httpd listens on all interfaces on the appropriate port, and that the DNS name someserver.net resolves to one of these addresses (usually, it should resolve to the external address, not to 127.0.0.1). So, the file /etc/hosts should NOT contain a line: 127.0.0.1 someserver.net Kind regards. Am 01.04.20 um 19:37 schrieb John Smith:
When trying to update data with POST, there comes: Can\'t connect to someserver.net:8092 <http://someserver.net:8092> (Connection timed out) No markings in apache's logs. Apache and application run in lxc container. If I call 127.0.0.1 or localhost instead of someserver, result is: 'Can\'t connect to localhost:8092 (Connection refused) Service works well, if it is called outside On Wed, Apr 1, 2020 at 6:57 PM Rich Bowen <rbo...@rcbowen.com <mailto:rbo...@rcbowen.com>> wrote: Please provide the error message, from the error log. On 4/1/20 9:47 AM, John Smith wrote: > Hello, > > When calling restapi (https://someserver.net/api/dosomething PUT or GET) > from localhost, it says Connection not allowed. From outside it works > well. A perl script is doing the calling. This might be an apache > configuration issue, or? > Regards, > John -- Rich Bowen - rbo...@rcbowen.com <mailto:rbo...@rcbowen.com> http://rcbowen.com/ @rbowen
