Страница 5 из 5

Удаленный узел закрыл соединение

Добавлено: 09 окт 2011, 18:34
Попытка соединения с сервером не удалась: Удаленный узел закрыл соединение
1. Проверьте правильность ввода адреса и порта сервера
2. Убедитесь, что сервер действительно запущен и проверьте соединение с сервером (описано в посте viewtopic.php?p=3619#p3619 )
3. Возможно Вас просто забанили. Возможен бан по IP или диапазону адресов, маске. Обратитесь к Администраторам данного сервера.
4. Вы превысили допустимое число подключений к серверу за определенный промежуток времени. Попробуйте немного позже.
5. Отключите фаерволы, брандмауэры.
6. Подключитесь к нашему Публичному серверу ( viewtopic.php?p=150#p150 ) Подключились? Значит проблема не у Вас. Закажите аренду сервера у нас viewtopic.php?p=1532#p1532

Очень часто всех дисконектит

Добавлено: 10 янв 2017, 21:30
Настройки сервера

Код: Выделить всё

# Murmur configuration file.
# General notes:
# * Settings in this file are default settings and many of them can be overridden
#   with virtual server specific configuration via the Ice or DBus interface.
# * Due to the way this configuration file is read some rules have to be
#   followed when specifying variable values (as in variable = value):
#     * Make sure to quote the value when using commas in strings or passwords.
#        NOT variable = super,secret BUT variable = "super,secret"
#     * Make sure to escape special characters like '\' or '"' correctly
#        NOT variable = """ BUT variable = "\""
#        NOT regex = \w* BUT regex = \\w*

# Path to database. If blank, will search for
# murmur.sqlite in default locations or create it if not found.

# If you wish to use something other than SQLite, you'll need to set the name
# of the database above, and also uncomment the below.
# Sticking with SQLite is strongly recommended, as it's the most well tested
# and by far the fastest solution.

# Murmur defaults to not using D-Bus. If you wish to use dbus, which is one of the
# RPC methods available in Murmur, please specify so here.

# Alternate D-Bus service name. Only use if you are running distinct
# murmurd processes connected to the same D-Bus daemon.

# If you want to use ZeroC Ice to communicate with Murmur, you need
# to specify the endpoint to use. Since there is no authentication
# with ICE, you should only use it if you trust all the users who have
# shell access to your machine.
# Please see the ICE documentation on how to specify endpoints.
#ice="tcp -h -p 6502"

# Ice primarily uses local sockets. This means anyone who has a
# user account on your machine can connect to the Ice services.
# You can set a plaintext "secret" on the Ice connection, and
# any script attempting to access must then have this secret
# (as context with name "secret").
# Access is split in read (look only) and write (modify) 
# operations. Write access always includes read access,
# unless read is explicitly denied (see note below).
# Note that if this is uncommented and with empty content,
# access will be denied.


# How many login attempts do we tolerate from one IP
# inside a given timeframe before we ban the connection?
# Note that this is global (shared between all virtual servers), and that
# it counts both successfull and unsuccessfull connection attempts.
# Set either Attempts or Timeframe to 0 to disable.
autobanAttempts = 0
#autobanTimeframe = 120
autobanTime = 0

# Specifies the file Murmur should log to. By default, Murmur
# logs to the file 'murmur.log'. If you leave this field blank
# on Unix-like systems, Murmur will force itself into foreground
# mode which logs to the console.

# If set, Murmur will write its process ID to this file
# when running in daemon mode (when the -fg flag is not
# specified on the command line). Only available on
# Unix-like systems.

# The below will be used as defaults for new configured servers.
# If you're just running one server (the default), it's easier to
# configure it here than through D-Bus or Ice.
# Welcome message sent to clients when they connect.
welcometext="<center><h1>Добро пожаловать в Lamussons</h1></center><br><center><img src='http://lamussons.ru/img/logo2.png' border='0' width='200' height='140'></center><br><br>
Сайт: <a href='http://lamussons.ru/'>Lamussons.ru</a><br> Устав: <a href='http://goo.gl/rkjOz8'>Прочитать</a><br>

# Port to bind TCP and UDP sockets to.

# Specific IP or hostname to bind to.
# If this is left blank (default), Murmur will bind to all available addresses.

# Password to join server.

# Maximum bandwidth (in bits per second) clients are allowed
# to send speech at.

# Maximum number of concurrent clients allowed.

# Amount of users with Opus support needed to force Opus usage, in percent.
# 0 = Always enable Opus, 100 = enable Opus if it's supported by all clients.

# Maximum depth of channel nesting. Note that some databases like MySQL using
# InnoDB will fail when operating on deeply nested channels.

# Regular expression used to validate channel names.
# (Note that you have to escape backslashes with \ )
channelname=[ \\-=\\w\\#\\[\\]\\{\\}\\(\\)\\@\\|№]+

# Regular expression used to validate user names.
# (Note that you have to escape backslashes with \ )

# Maximum length of text messages in characters. 0 for no limit.

# Maximum length of text messages in characters, with image data. 0 for no limit.

# Allow clients to use HTML in messages, user comments and channel descriptions?

# Murmur retains the per-server log entries in an internal database which
# allows it to be accessed over D-Bus/ICE.
# How many days should such entries be kept?
# Set to 0 to keep forever, or -1 to disable logging to the DB.

# To enable public server registration, the serverpassword must be blank, and
# this must all be filled out.
# The password here is used to create a registry for the server name; subsequent
# updates will need the same password. Don't lose your password.
# The URL is your own website, and only set the registerHostname for static IP
# addresses.
# Only uncomment the 'registerName' parameter if you wish to give your "Root" channel a custom name.
registerName=Lamussons Server

# If this option is enabled, the server will announce its presence via the 
# bonjour service discovery protocol. To change the name announced by bonjour
# adjust the registerName variable.
# See http://developer.apple.com/networking/bonjour/index.html for more information
# about bonjour.

# If you have a proper SSL certificate, you can provide the filenames here.
# Otherwise, Murmur will create it's own certificate automatically.

# The sslCiphers option chooses the cipher suites to make available for use
# in SSL/TLS. This option is server-wide, and cannot be set on a
# per-virtual-server basis.
# This option is specified using OpenSSL cipher list notation (see
# https://www.openssl.org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT).
# It is recommended that you try your cipher string using 'openssl ciphers <string>'
# before setting it here, to get a feel for which cipher suites you will get.
# After setting this option, it is recommend that you inspect your Murmur log
# to ensure that Murmur is using the cipher suites that you expected it to.
# Note: Changing this option may impact the backwards compatibility of your
# Murmur server, and can remove the ability for older Mumble clients to be able
# to connect to it.

# If Murmur is started as root, which user should it switch to?
# This option is ignored if Murmur isn't started with root privileges.

# If this options is enabled, only clients which have a certificate are allowed
# to connect.

# If enabled, clients are sent information about the servers version and operating
# system.

# You can configure any of the configuration options for Ice here. We recommend
# leave the defaults as they are.
# Please note that this section has to be last in the configuration file.

# AFK канал 
defaultchannel = 17

характеристики сервера

1x2.2ГГц, 2Гб RAM, 40Гб HDD

Re: Удаленный узел закрыл соединение

Добавлено: 13 янв 2017, 12:07
Если у Вас возникают проблемы с подключением к серверу - пожалуйста, выполните инструкции описанные в посте viewtopic.php?p=3619#p3619

Re: Удаленный узел закрыл соединение

Добавлено: 21 янв 2017, 19:00
Попытка соединения с сервером не удалась: Удалённый узел закрыл соединение.

Код: Выделить всё

C:\Users\Сергей>tracert m.voice-server.ru

Трассировка маршрута к m.voice-server.ru []
с максимальным числом прыжков 30:

  1    <1 мс    <1 мс    <1 мс
  2     1 ms     1 ms     1 ms
  3    <1 мс     3 ms    <1 мс
  4     *        *        *     Превышен интервал ожидания для запроса.
  5     1 ms     1 ms     1 ms
  6     1 ms     1 ms     3 ms  ae3.RT.ATR.NIK.UA.retn.net []
  7    25 ms    25 ms    25 ms  ae3-2.RT.MR.MSK.RU.retn.net []
  8    24 ms    24 ms    24 ms  GW-Selectel.retn.net []
  9    25 ms    28 ms    26 ms  01.msk.net.selectel.ru []
 10    24 ms    23 ms    24 ms

Трассировка завершена.

Код: Выделить всё

C:\Users\Сергей>pathping m.voice-server.ru

Трассировка маршрута к m.voice-server.ru []
с максимальным числом прыжков 30:
  0  Falazur []
  4     *        *        *
Подсчет статистики за: 75 сек. ...
           Исходный узел     Маршрутный узел
Прыжок  RTT   Утер./Отпр.   %   Утер./Отпр.  %   Адрес
  0                                           Falazur []
                                0/ 100 =  0%   |
  1    0мс     0/ 100 =  0%     0/ 100 =  0%
                                0/ 100 =  0%   |
  2    1мс     0/ 100 =  0%     0/ 100 =  0%
                                0/ 100 =  0%   |
  3    0мс     0/ 100 =  0%     0/ 100 =  0%

Трассировка завершена.

Re: Отказано в соединении. Connection refused

Добавлено: 05 май 2017, 18:53
Добрый день! Не могу подключится к серверу, пишет: [18:37:57] Попытка соединения с сервером не удалась: Удалённый узел закрыл соединение.
Что делать как быть? К остальным серверам норм подключается!
Вин 10, Mumble 1.2.15.