# crawler is blocked port 80 but 443

**URL:** <https://discuss.codelibs.org/t/crawler-is-blocked-port-80-but-443/931>\
**Category:** English:Fess\
**Created:** [May 31, 2016, 2:43pm UTC](https://discuss.codelibs.org/t/crawler-is-blocked-port-80-but-443/931 "2016-05-31T14:43:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![discuss](https://discuss.codelibs.org/user_avatar/discuss.codelibs.org/discuss/32/298_2.png) [@discuss](https://discuss.codelibs.org/u/discuss)\
**Post date:** [May 31, 2016, 2:43pm UTC](https://discuss.codelibs.org/t/crawler-is-blocked-port-80-but-443/931/1 "2016-05-31T14:43:44Z")

</div>

(from [github.com/ndrwchn](http://github.com/ndrwchn))  
It seems weird to me. Once crawlering a certain website, like [http://xxx.xxx.com/](http://xxx.xxx.com/), no indexing result. However, using [https://xxx.xxx.com/](https://xxx.xxx.com/), no issue. By using curl to test, port 80 bounces ‘connection refused’, 443 is OK. Both 80 and 443 are OK in browser.

My question is how this happened? It seems block FESS in firewall not by TCP port, but by app name? What’s robot name for FESS?

---

<div class="post-metadata">

**Author:** ![discuss](https://discuss.codelibs.org/user_avatar/discuss.codelibs.org/discuss/32/298_2.png) [@discuss](https://discuss.codelibs.org/u/discuss)\
**Post date:** [May 31, 2016, 8:37pm UTC](https://discuss.codelibs.org/t/crawler-is-blocked-port-80-but-443/931/2 "2016-05-31T20:37:49Z")

</div>

(from [github.com/marevol](http://github.com/marevol))  
Changing user-agent on web crawling config, it may work.  
[http://fess.codelibs.org/10.0/admin/webconfig-guide.html#user-agent](http://fess.codelibs.org/10.0/admin/webconfig-guide.html#user-agent)
