• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

ports 6346 and 6699?

ArmandoC

New Pleskian
Hi, everybody, i'have installed my web server with plesk and before to use in production i have done a
nmap

I have seen that there are port 6346 and 6699 (gnutella and napster) filtered....but i don't have done anything with these ports!!! What's the meaning?
 
I see nothing for these ports on default Plesk installation:

-bash-4.1# lsof -i tcp:6346
-bash-4.1# lsof -i tcp:6699

Or you had these ports previously and after Plesk installation they became filtered?
 
I have, also, do

# lsof -i tcp:6346
# lsof -i tcp:6699

and...nothing!
if i do
iptables -L
there aren't any row for the ports 6699 or 6346

...mmmm
 
i have, also
# lsof -i tcp:6346
# lsof -i tcp:6699
and nothing....this maening that ports are closed?

if i do
iptables -L
there aren't any rows for ports 6699 or 6346
...mmmm
 
And what? Why you do not check other ports? 9781, for example?
I do not understand why you're so worried about the ports that are not even open?
 
If you haven't any output of commands

-bash-4.1# lsof -i tcp:6346
-bash-4.1# lsof -i tcp:6699
-bash-4.1# netstat -anp | grep 6699
-bash-4.1# netstat -anp | grep 6346

you shouldn't worry about these ports. They are not active. And they are absolutely not related to Plesk.
 
Back
Top