Find the answer to your Linux question:
Results 1 to 2 of 2
I have Fedora 12 behind squid proxy, which is running locally on my PC. On my NAS i have installed Transmission bit-torrent that can be accessed via its web interface. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    163

    Question [SOLVED] Squid proxy blocking transmission's web interface


    I have Fedora 12 behind squid proxy, which is running locally on my PC. On my NAS i have installed Transmission bit-torrent that can be accessed via its web interface.
    Normally when I connect to the transmission's web interface the pop-up window appears asking for credentials. However when squid proxy is activated the following error message appears:
    The requested URL could not be retrieved
    Read Error
    The system returned: (107) Transport endpoint is not connected


    Transmission daemon is functioning normally (I can use it from Windows, or when I bypass the squid proxy). Therefore I assume that squid configuration should be changed, but I'm not 100% sure because transmission configuration contains some security settings as well.

    Can someone help me to identify which squid/transmission configuration parameters are responsible for this behavior?
    Last edited by blnl; 04-21-2010 at 08:37 AM.
    Fedora20.GNOME@Dell_Latitude_E6410
    Fedora14.GNOME@HP_Compaq_DC7100

  2. #2
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    163

    Thumbs up

    Solution:

    change SELinux policy for transmission port
    Code:
    semanage port -a -t http_port_t -p tcp #PORT
    See 165586-solved-help-squid-transmission-selinux.html
    Fedora20.GNOME@Dell_Latitude_E6410
    Fedora14.GNOME@HP_Compaq_DC7100

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •