Luke, Lets keep this on the list please.
The best test is to see on the server that you can get to Pootle. If you can and you can't from outside the server then somehow to connection to Pootle is blocked. You want to make sure that the correct ports are open and available. On 13 April 2015 at 10:14, Luke van Velthoven <[email protected]> wrote: > Thanks! I've worked with Windows almost exclusively, so those ideas > don't occur to me yet. :) > > Now I get this on my own PC (in Chrome), really seems to be a problem > on ICT's end indeed: > > Google Chrome's connection attempt to pootle was rejected. The website > may be down, or your network may not be properly configured. > Check your Internet connection > Check any cables and reboot any routers, modems, or other network > devices you may be using. > Allow Chrome to access the network in your firewall or antivirus settings. > If it is already listed as a program allowed to access the network, > try removing it from the list and adding it again. > If you use a proxy server... > Check your proxy settings or contact your network administrator to > make sure the proxy server is working. If you don't believe you should > be using a proxy server: Go to the Chrome menu > Settings > Show > advanced settings...> Change proxy settings... > LAN Settings and > deselect "Use a proxy server for your LAN". > Error code: ERR_CONNECTION_REFUSED > > Thanks for your help! > > Regards, > Luke > > 2015-04-13 10:58 GMT+02:00 Dwayne Bailey <[email protected]>: > > Luke, if you get such an error try look back in the logs to see what > might > > have caused it. In this case it looks like ln227 we're missing the > 'assets' > > directory, please make that and rerun collectstatic and assets build > > commands. > > > > On 13 April 2015 at 09:45, Luke van Velthoven <[email protected]> > wrote: > >> > >> Hi, > >> > >> Thanks for your responses! I finally got the VM in my own hands and > >> this has been my progress so far: http://pastebin.com/hpKYMAfq > >> > >> To keep things as simple as possible, I am just trying that standard > >> build again. If the tools suit our needs, we can look at a MySQL > >> database again. :) > >> > >> As you can see, I get the 'collectstatic' and 'assetsbuild' errors > >> again. I already tried version 2.5.1, but got another error (this one: > >> http://sourceforge.net/p/translate/mailman/message/32924968/). > >> > >> So, if I can get these two commands to work, I can start trying to > >> ping the server again and see what's the problem on that front! > >> > >> Kind regards, > >> Luke van Velthoven > >> > >> 2015-04-09 19:05 GMT+02:00 Dwayne Bailey <[email protected]>: > >> > For a proper install I have to concur that you must run this with > apache > >> > or > >> > nginx see http://pootle.readthedocs.org/en/latest/server/web.html for > >> > some > >> > pointers. > >> > > >> > pootle start will run on port 8000 and you server has to be allowing > >> > traffic > >> > out on that port. If you can ping it on the server (and access it > >> > through a > >> > browser on the server then that is the problem). You can try run > pootle > >> > start on another port - I think that is possible --help should guide > you > >> > there. > >> > > >> > MySQL setup is relatively simple so I'd also be curious as to what the > >> > errors are. That said sqlite for now is OK, just don't deploy on it. > >> > > >> > On 8 April 2015 at 16:23, Steven Garrad <[email protected]> wrote: > >> >> > >> >> By default the pootle service runs off port 8000. If you have a > virtual > >> >> machine, make sure you have port forwarding to that machine. You > >> >> however are > >> >> likely better off running it via apache or nginx. > >> >> Also what errors were you getting with the mysql connection? Was it > on > >> >> the > >> >> same machine as the pootle instance? > >> >> > >> >> -Steve > >> >> > >> >> > Date: Wed, 8 Apr 2015 17:19:03 +0200 > >> >> > From: [email protected] > >> >> > To: [email protected] > >> >> > Subject: [translate-pootle] Trying Pootle in a business > environment, > >> >> > but failing so far > >> >> > > >> >> > Hi! > >> >> > > >> >> > We are currently trying out Pootle in our own network, but we can't > >> >> > seem to get it to work. I already installed Pootle successfully at > >> >> > home, so I don't know why it isn't working over here. Perhaps > >> >> > (hopefully) you guys can help us out. > >> >> > > >> >> > We're running Pootle on a Debian VM and did the following: > >> >> > > >> >> > 1. $ sudo -s > >> >> > > >> >> > 2. root$ apt-get install python-dev libxml2-dev libxslt1-dev > >> >> > > >> >> > 3. root $ apt-get install python-pip > >> >> > > >> >> > 4. root$ pip install virtualenv > >> >> > > >> >> > 5. root$ virtualenv /var/www/pootle/env/ > >> >> > > >> >> > 6. root$ source /var/www/pootle/env/bin/activate > >> >> > > >> >> > 7. (env)root$ pip install pootle==2.5.1.1 > >> >> > > >> >> > 8. (env)root$ pootle --version > >> >> > > >> >> > 9. (env)root$ pootle init > >> >> > > >> >> > 10. (env)root$ pootle setup > >> >> > > >> >> > 11. (env)root$ pootle collectstatic --noinput > >> >> > > >> >> > 12. (env)root$ pootle assets build > >> >> > > >> >> > 13. (env)root$ pootle start > >> >> > > >> >> > We ran into two problems: we first tried to use a proper MySQL > >> >> > database, but got too many errors with that. So, since this is > just a > >> >> > test for the tool itself, we went with the 'simple' installation. > >> >> > However, we can't seem to reach the Debian machine and we don't > know > >> >> > why. We can ping the Pootle application from the Debian console > >> >> > itself, but all browers in our network say it can't connect. Any > >> >> > ideas > >> >> > for us? > >> >> > > >> >> > Thanks in advance! > >> >> > > >> >> > Kind regards, > >> >> > Luke van Velthoven > >> >> > > >> >> > > >> >> > > >> >> > > ------------------------------------------------------------------------------ > >> >> > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > >> >> > Develop your own process in accordance with the BPMN 2 standard > >> >> > Learn Process modeling best practices with Bonita BPM through live > >> >> > exercises > >> >> > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- > >> >> > event?utm_ > >> >> > > >> >> > > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > >> >> > _______________________________________________ > >> >> > Translate-pootle mailing list > >> >> > [email protected] > >> >> > https://lists.sourceforge.net/lists/listinfo/translate-pootle > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ > >> >> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > >> >> Develop your own process in accordance with the BPMN 2 standard > >> >> Learn Process modeling best practices with Bonita BPM through live > >> >> exercises > >> >> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- > >> >> event?utm_ > >> >> > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > >> >> _______________________________________________ > >> >> Translate-pootle mailing list > >> >> [email protected] > >> >> https://lists.sourceforge.net/lists/listinfo/translate-pootle > >> > > >> > > >> > > >> > > >> > -- > >> > Dwayne > >> > > >> > Translate > >> > +27 12 460 1095 (work) > > > > > > > > > > -- > > Dwayne > > > > Translate > > +27 12 460 1095 (work) > -- Dwayne *Translate* +27 12 460 1095 (work) ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
