Author Topic: Please make MFP use higher port numbers to stop problems in viewing statements.  (Read 1244 times)

Tags:
  • All members
  • Posts: 28
I've seen MarketFeeder Pro use high-ish port numbers every now and then for viewing statements, which is good, but nearly all the time now on my computer it is using low port numbers which is causing problems with viewing statements.  I'm also getting the logging problem reported at http://community.welldonesoft.com/troubleshooting-8/what-this/msg40569/#msg40569. which also seems to be caused by low port numbers being used.

If I open a first instance of MFP it uses port 2 (or something around port 2) for viewing statements which works OK, although not good practise as far as I understand (see a few paragraphs below), as port 2 is also a "well-known" port for CompressNET.
Once I open a few more instances of MFP, and get to port 7 or so, I start getting problems including:

If I try to view a statement I get the following message in my browser:

"This webpage is not available

ERR_UNSAFE_PORT"

....and the logging problem reported in the link above.

For example I'm trying to view a statement and MPF points my browser to  http://127.0.0.1:9/#statement;;test

So as we can see from the URL, MFP is pointing my browser to port 9 and the browser really, really doesn't like that!  The same occurs at other low port numbers (though not all - it can take ages for me to juggle my MPF instances around to get statements and logging working correctly)

Instead of using low port numbers, resulting in these frustrating logging problems, please could MFP be set up to use higher port numbers, for example the "dynamic port range of 49152 to 65535.

As far as I understand, as well as avoiding the statement and logging problems, it good practise to use higher port numbers, ie the "dynamic ports" from 49152 to 65535.  This seems to be recommended by IANA rather than using "well-known" or "system"ports (0 to 1023) and "Registered Ports:" (1024 to 49151) (see for example  http://tools.ietf.org/html/rfc6335#section-8.1.2 )

I'm loving Marketfeeder Pro but these logging problems cause by the low port numbers are really stressing me out and causing huge amounts of wasted time.

  • Tim Vetrov
  • Administrator
  • Posts: 4870
  • Gender: Male
*
To be honest MF used to use 19001 port... But it seems like a bug in the latest build. Going to fix it asap. Sorry for inconvenience.
Proud to be 🇺🇦
I'm happy to help Monday - Friday, 08:00-18:00 GMT
Буду рад помочь с понедельника по пятницу, 08:00-18:00 GMT

  • All members
  • Posts: 28
Thanks Tim  - looking forward to the fix.

 

Please note, BetFair is seems to be currently OFFLINE