Access to the MyChat WEB server from the outside is required for three things:

  1. file/image transfer/update system;
  2. connection of Android/iOS mobile clients;;
  3. operation of any MyChat web services (admin panel, kanban board, forum, web chat, MyChat Guest, Integration API via REST, support chat on the website, lobby).

 

If you correctly configured port mapping (port forwarding etc., the names may differ in the Admin Panel of your router) for the specified TCP port, and everything is fine with other ports, butа MнChat WEB server port is unavailable, then check the following:

 

  • 80 TCP port usually occupied by Admin Panel or a router;
  • IIS or Apache web servers may be running on port 80 on your computer and you will not be able to reuse it;
  • you configured port forwarding incorrectly. For example, you "listen" to TCP port 8083 at the router's input "outside", and forward it to TCP 80 inside the local network. This is not correct, the port cannot be changed "on the fly";
  • TCP port 80 may be closed by a firewall or antivirus on the computer whe MyChat Server installed;
  • in MyChat Server Admin Panel, the section IP filters, incorrectly configured rules for incoming connections;
  • One or another feature is physically disabled in the WEB service settings. For example, lobby, web chat, and kanban are disabled. This is also worth checking.

 

What to do?

Change the default TCP 80 (http) or TCP 443 (https) port on your MyChat server to something else, for example 8080, forward it on your router instead of 80/443. If everything is fine, it means that the previous port was busy. To find out by what exactly, you can open the internal IP address of your router in your browser. This is usually the field "default gateway" in console command ipconfig:

 

> ipconfig

Configuring IP for Windows

 

Wireless LAN adapter Wireless network:

 

  DNS suffix of the connection . . . . . : www.tendawifi.com

  Local IPv6-address of the channel канала . . . : fe80::c1c6:b759:ae72:5b35%8

  IPv4 address. . . . . . . . . . . . : 192.168.0.192

  Subnet mask . . . . . . . . . . : 255.255.255.0

Main gateway . . . . . . . . . : 192.168.0.1

 

Adapter Ethernet Network connection Bluetooth:

 

  Environment state. . . . . . . . : Transfer environment is unavailable.

  DNS suffix of the connection подключения . . . . . :

Created with the Personal Edition of HelpNDoc: Elevate your documentation to new heights with HelpNDoc's built-in SEO