logdog

Can you unarchive my account logdog?

I PM'd you additional details.

Request allowing tcp dest port 8088 outbound.

This is for connecting to Splunk cloud test drive instance.

They don't let you change the receiving port.

Thanks!

That explains a lot.

I was creating some files on Windows and some locally in cpanel/editor, thus the mixed results.

I'm on johnny.

both files in cgi-bin w/ 755

This  (lf37.py) gives me 500 error

This (lf27.py) works

Please advise.

Thanks @leogama.  I copied everything you did and it worked for me.  Now I have a base to try my app from.

RE: the wiki, I'm not sure what the best way to fix it is (one hello dir or two?)

Thanks for the help.

The content in the wiki has a contradiction

On local host, you have  two hello dirs

../hello/manage.py

../hello/hello/dispatch.wsgi

The tree output (right after the allowed_hosts section of wiki) shows that the project content was uploaded directly to public_html/  So, the top level hello is not on heliohost

you have:

../public_html/manage.py

../public_html/hello/dispatch.wsgi

The contradiction comes in the .htaccess file in the wiki.  It shows two hello levels whereas there is only one on heliohost per the tree output.

RewriteRule ^(.*)$ hello/hello/dispatch.wsgi/$1 [QSA,PT,L]

@leogama, sounds like you got it working by not putting project content in your public_html.  In other words, you kept the top level "hello"

Can you share your tree view, .htaccess and dispatch.wsgi?

Having problem getting Django app to work.

Did all the steps here http://www.heliohost.org/classic/features/languages/python

Is there anything that needs to be done to turn on Django/Python for the account?

Or, is there anyway to get some error output for troubleshooting?

My project name is h1

Creating a project you get an h1 dir and another one named h1 dir under it.

So location for dispatcher is

public_html/h1/h1/dispatcher.wsgi

have also created

public_html/h1/media/test.html

I tested the media exemption and it works fine, so I think there needs to be some extra h1 dirs in the .htaccess

similar to the inforiesgoserver/inforiesgoserver/... in this example:  https://www.helionet.org/index/topic/29558-django-project-not-working/

It appears that the filter regex is relative to the location of the .htaccess (../public_html/h1/)  and the target is relative to the account root (../public_html/)

Something like this:

But, that does not work either.

Please advise.