Announcement

Collapse
No announcement yet.

Webserver error and strange file requests

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Webserver error and strange file requests

    Over the last few days I've been seeing this error in the log:
    Code:
    [COLOR="Orange"]Warning	Webserver accept callback: An existing connection was forcibly closed by the remote host[/COLOR]
    But today I saw this:

    Code:
    [COLOR="orange"]Dec-21 3:26:55 PM	 	Warning	File does not exist: C:\Program Files\HomeSeer HS3\htmlhttp:\www.baidu.com\cache\global\img\gs.gif
    Dec-21 3:26:55 PM	 	Warning	Webserver accept callback: An existing connection was forcibly closed by the remote host[/COLOR]
    Why would HS3 be looking for a file from baidu.com?

    #2
    This is most likely a spammer probing your HSTouch server and when the connection times out you get the forcibly closed message. They are also most likely trying to do a put on your web server using the URL you listed. Are you using "Enable IP Hack Blocking" which can help prevent this.
    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

    Comment


      #3
      I have one similar but not the same:

      Feb-20 14:37:53 Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\htmlhttp:\www.baidu.com\favicon.ico

      It happens when I restart the system after a reboot.

      Michael
      HS3Pro & HS4Pro on Win2012R2
      Aeotec, Cooper, Cree, GE/Jasco, Intermatic, LIFX, Fortrezz, OSRAM, RCS, Trane, Zooz
      BLBackup, BLGData, BLRussound, BLSpeech, HSTouch, InvisaLink, HSBuddy, IFTTT, JowiHue, NetCAM, PHLocation, Pushover 3P, Random, rnbWeather, UltraLighting3, weatherXML, ZigBee, Z-Wave

      Comment


        #4
        Originally posted by Jobee View Post
        I have one similar but not the same:

        Feb-20 14:37:53 Warning File does not exist: C:\Program Files (x86)\HomeSeer HS3\htmlhttp:\www.baidu.com\favicon.ico

        It happens when I restart the system after a reboot.

        Michael
        This sounds like it could be an XSS issue. What was being loaded up when you see that message post to the log?

        Comment

        Working...
        X