Refused to connect 2022

SYSTEM INFORMATION
OS type and version REQUIRED
Webmin version REQUIRED

This is the second times, I come back to try winmin + virtualmin, both time I have paid, however, it is not smooth on my testing.

Actually, I have another server which is directadmin, I rent it from another hosting server, whatever I need, they can do it for me, although, the layout is old, but it can do what i want.

My second time to try virtual admin,
the first time i stopped as i am busy. but it is worst than last time.

My process is :
I have created a virtual server, sucms.mydomain1.com ( choose auto create user )
and i create another virtual server . sucms.mydomain2.com ( do th same, but error, said like :“no existing unix user exists” , Oh my god, i completely don’t know what happen)

whatever, the first virtual server create sucms user, then i put second server to sucms user, success

then i access the subserver, i see there are option(s), then i just tick some,

save

then the connection is broken .: chrome : refused to connect

I just want to play simple, i have not try any difficult setting, such as : auto binding subdomain base on the folder ( i know directadmin can do this).

it is my first day paid on second time testing, i drop into testing mode…god ! I am not server professional, but i am well in writing web program only…

I am really sad, the bug happen so soon. i don’t know how many will coming. if it is not bug, must be my operation mistake?

could you tell me what i can do …
i don’t know if i can continue for just using a another free web control panel ?

:’(

More details:

[root@server ~]# service webmin status
Redirecting to /bin/systemctl status webmin.service
● webmin.service - Webmin server daemon
   Loaded: loaded (/usr/lib/systemd/system/webmin.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Fri 2022-06-03 14:18:38 UTC; 4min 40s ago
  Process: 6235 ExecStop=/etc/webmin/.stop-init (code=exited, status=0/SUCCESS)
 Main PID: 13668 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/webmin.service
           └─2433 /usr/libexec/webmin/virtual-server/lookup-domain-daemon.pl

Jun 03 14:18:30 server.mydomain.com su[5938]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5943]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5956]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5962]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5974]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5979]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5987]: (to sucms) root on none
Jun 03 14:18:30 server.mydomain.com su[5994]: (to sucms) root on none
Jun 03 14:18:38 server.mydomain.com webmin[13668]: Webmin starting
Jun 03 14:18:38 server.mydomain.com .stop-init[6235]: Stopping Webmin server in /usr/libexec/webmin

Hello,

There was a bug that allowed Webmin to be killed by OOM in case of a low RAM. Upcoming Webmin 1.995 will have this issue sorted out.

However, the real source of the issue is a system which is low on RAM.

Note, that clamd and/or clamscan (virus scanning) cannot be used/enabled on systems with low RAM.

in my view, if it is low ram,

i suggest to give a tips tell user (root user ) ,what will happen in low ram.

or turn off some feature ( which not necessary) , and user (root user ) can turn is on step by step, but some user guide.

it user need a lot of feature, then need more ram, it is reasonable.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.