My guess is that you enabled the webservice, which is currently broken (a relic from ABC which we failed to test for this release apparently). To disable it again, you should edit the webservice.conf file in C:\Documents and Settings\user\Application Data\.Tribler and setting webautostart to 0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The webservice.conf file was missing because I had not started the web interface service
under tools. I have done this, clicking on it to start automatically when I start Tribler.
The file then appeared and I altered it placing a zero instead of a 1, then saving it.
It made no difference, the yellow exclamation mark still appearing.
I have started tribler with the windows firewall stopped which made no difference, so
I suspect it may not be a firewall problem.
Now that I look at the log again, I also notice that a connection we make at startup to our web server fails. If you cannot connect to this machine for some reason, Tribler may conclude you are not reachable. However, you also report that you cannot connect to Tribler by hand, which would not be explained by a problem with setting up outgoing connections.
Could you try
telnet www.tribler.org 80
and see if you get a connection?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried the Telnet command and ended up with a blank screen.
When I typed quit the attachment was displayed.
I have no desire to hog this bug report area with my
problems and I'm sure that you have enough work to do
without my problem. If you wish, you can contact me at
priaprism@hotmail.com which would save me filling this
up with my postings.
Someone advised that I should disable UPnP in the Tribler
preferences since I have a port forwarding entry in my Airport
Extreme router. This made no difference.
In the meantime, I'll continue to play around with it
to see if I can get rid of that exclamation mark. Maybe
an updated version will work OK.
Thanks for your help.
File Added: telnet.jpg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tribler now working. The perplexing yellow exclamation mark
replaced by a white arrow/green background. What I did was to
enter a port number in the 49000's in the port forwarding section of my Airport Extreme router as well as 10.0.1.199.
This did the trick. Thanks for your help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
exe.log file
Logged In: YES
user_id=216477
Originator: NO
My guess is that you enabled the webservice, which is currently broken (a relic from ABC which we failed to test for this release apparently). To disable it again, you should edit the webservice.conf file in C:\Documents and Settings\user\Application Data\.Tribler and setting webautostart to 0
Logged In: YES
user_id=1520742
Originator: YES
Thank you for the information. Unfortunately the folder in question
does not contain the file you specify.
File Added: Folder.jpg
Logged In: YES
user_id=1520742
Originator: YES
The webservice.conf file was missing because I had not started the web interface service
under tools. I have done this, clicking on it to start automatically when I start Tribler.
The file then appeared and I altered it placing a zero instead of a 1, then saving it.
It made no difference, the yellow exclamation mark still appearing.
I have started tribler with the windows firewall stopped which made no difference, so
I suspect it may not be a firewall problem.
[ABC/Webservice]
allow_resume = 1
allow_stop = 1
allow_clearcompleted = 1
webport = 56667
webid =
allow_query = 1
allow_delete = 1
webautostart = 0
allow_pause = 1
webip = Automatic
allow_add = 1
allow_getparam = 0
allow_queue = 1
allow_setprio = 1
allow_setparam = 0
priaprism@hotmail.com
Logged In: YES
user_id=216477
Originator: NO
Now that I look at the log again, I also notice that a connection we make at startup to our web server fails. If you cannot connect to this machine for some reason, Tribler may conclude you are not reachable. However, you also report that you cannot connect to Tribler by hand, which would not be explained by a problem with setting up outgoing connections.
Could you try
telnet www.tribler.org 80
and see if you get a connection?
Logged In: YES
user_id=1520742
Originator: YES
I tried the Telnet command and ended up with a blank screen.
When I typed quit the attachment was displayed.
I have no desire to hog this bug report area with my
problems and I'm sure that you have enough work to do
without my problem. If you wish, you can contact me at
priaprism@hotmail.com which would save me filling this
up with my postings.
Someone advised that I should disable UPnP in the Tribler
preferences since I have a port forwarding entry in my Airport
Extreme router. This made no difference.
In the meantime, I'll continue to play around with it
to see if I can get rid of that exclamation mark. Maybe
an updated version will work OK.
Thanks for your help.
File Added: telnet.jpg
Logged In: NO
Tribler now working. The perplexing yellow exclamation mark
replaced by a white arrow/green background. What I did was to
enter a port number in the 49000's in the port forwarding section of my Airport Extreme router as well as 10.0.1.199.
This did the trick. Thanks for your help.