nuk

Am I unable to connect to my account via FTP (to upload files to public_html) because there's an error with Tommy, or is it more likely a network mis-configuration on my end? FWIW, I had no trouble several years ago, so I think it's a little more than just user error. Then again, that was connecting to Stevie, not Tommy, and from a completely different home network as well. Details of what I'm doing: Using FileZilla (v3.24.0 on Win10) with the imported configurations available through cPanel, I've attempted to connect to my account on Tommy with both SFTP and FTP, but am getting an error I do not know how to resolve. With SFTP: Status: Connecting to ftp.ukanuk.heliohost.org:1342... Status: Connected to ftp.ukanuk.heliohost.org Status: Retrieving directory listing... Command: pwd Response: Current directory is: "/home/ukanuk" Error: Failed to parse returned path. Error: Failed to retrieve directory listing With FTP: Status: Resolving address of ftp.ukanuk.heliohost.org Status: Connecting to 65.19.143.6:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Logged in Status: Retrieving directory listing... Command: PWD Response: 257 "/" is your current location Command: TYPE I Response: 200 TYPE is now 8-bit binary Command: PASV Response: 227 Entering Passive Mode (65,19,143,6,162,142) Command: MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing

It doesn't matter that much, it can stay ukanuk. I like using "nuk" to register for sites, but there's plenty where it's already taken and I have to use something else. I just thought it strange because I used to have "nuk" as the username for both my hosting and forum accounts, and I had assumed I'd be able to have it that way again. Thanks again for all you're doing!

I've been a happy camper on Stevie for several years, and am still so thankful for the great service you guys provide despite the last few hard months! You guys definitely go above and beyond. One question: I just signed up for my new account on Tommy (since Stevie is gone forever), but it wouldn't let me reuse my old username. Is there any chance you guys can change it back to my old one, or has someone else already taken it? Old username: nuk New username: ukanuk (would prefer this changed back to nuk) Domain: ukanuk.heliohost.org

I've removed the semicolons, but I don't think that's changed anything. I was able to properly load http://ukanuk.heliohost.org/django2/polls/5/, so it seems like even if it isn't correct, it's still getting through. I was successful at fixing the admin page, at least as concerns accessing the database (I haven't messed with getting the static directory with its CSS files yet, so I'm assuming fixing that'll fix the styling issues). The fix was to change the permissions for the django2 directory (NOT recursively) from 555 to 777. Concerning the second error, I think the built-in (local, non-web) django server must just be configured slightly differently, because if I remove all the url patterns from /mysite/urls.py, then I get the proper "It worked! Congratulations on your first Django-powered page" message. As soon as I configure any URLs, then it stops working. I'll assume that this error is inconsequential, if slightly inconvenient. Hopefully once I have a nice sample site I can write a little tutorial in this forum explaining how to set it up, and with Python 3.4

I've installed Django 1.6.5 on my site on Stevie at http://ukanuk.heliohost.org/django2/. I'm creating the Basic Poll App Admin Site outlined at https://docs.djangop...m/en/1.6/intro/, I've mostly gotten through Part 3, and it works without flaw locally on my computer. My two problems upon uploading to Heliohost, hopefully related, are: 1. The admin page isn't working properly. When I try to log in, it gives me this error page, where I think is the pertinent info is after the second question. 2. The root directory is not giving me a page saying something like http://ukanuk.helioh...org/djangotest/ (which uses Stevie's Django v1.3.0), as it does locally on my computer. My sample app here, however, utilizing all sorts of URL mumbo-jumbo, works perfectly. Pertinent Error Page Info (Complete page here): OperationalError at /admin/ unable to open database fileRequest Method: POST Request URL: http://ukanuk.helioh.../django2/admin/ Django Version: 1.6.5 Exception Type: OperationalError Exception Value: unable to open database file Exception Location: /home/nuk/Django-1.6.5/django/db/backends/sqlite3/base.py in execute, line 451 Python Executable: /usr/bin/python Python Version: 2.7.1 Context: The default Django admin site utilizes SQLite for its database, and according to http://www.heliohost...atabases/sqlite the Python version should be 3.3.6, whereas my site is using the Stevie default 2.7.1. However, this Python version conflict seems improbable to me since SQLite embeds itself as a library instead of getting run by the server in its own script, and am running it locally with v2.7. In addition, "Exception Location of /home/nuk/Django-1.6.5/django/db/backends/sqlite3/base.py" above makes it seem like its using SQLite files bundled with Django. I think it more likely that there is some problem in my .htaccess, urls.py, or dispatch.wsgi files, but I'm not really sure where to start. I have no idea why Problem #2 is happening beyond a problem in my .htaccess, urls.py, or dispatch.wsgi. Maybe it's easier to solve than #1, and maybe fixing it will fix #1 too, or vice versa. /django2/.htaccess file RewriteEngine On RewriteBase / RewriteRule ^(static/.*)$ - [L] RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(dispatch\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ django2/dispatch.wsgi/$1 [QSA,PT,L] /django2/mysite/urls.py from django.conf.urls import patterns, include, url from django.contrib import admin admin.autodiscover() urlpatterns = patterns('', url(r'^polls/', include('polls.urls')), url(r'^admin/', include(admin.site.urls)), ) /django2/dispatch.wsgi import os, sys sys.path.insert(1,'/home/nuk/Django-1.6.5'); sys.path.append("/home/nuk/public_html/django2"); sys.path.append("/home/nuk/public_html/django2/mysite"); os.environ.setdefault("DJANGO_SETTINGS_MODULE", "mysite.settings") os.environ.setdefault("PYTHON_EGG_CACHE", "/home/nuk/.python_egg_cache") from django.core.wsgi import get_wsgi_application application = get_wsgi_application() I have also noticed that the admin site isn't properly getting its stylesheets, but I think this is probably just because I haven't properly set up my static files yet so I'm not as concerned about this. Any ideas?

So when is this content officially closed and the results in? I thought it was only a month, but it's already been a week more than that.... [](/rarityjudge)

No, that wasn't the problem. I have it working now, but it's telling me that the incoming server stevie.heliohost.org is encrypted with STARTTLS, not SSL. In any case, to get it working I had to do something really weird: set up the SMTP server separately (Edit -> Account Settings -> Outgoing Server (SMTP) -> Add -> fill in information). Then when I created my account I chose that as my outgoing server in the dropdown box for outgoing servers instead of setting up a new one. Also, I had to set "Your name: (as shown to others)" to be contact+ukanuk.heliohost.org (the same as the Username field).

OK, the online interface is showing my messages now, but I still can't get TB configured properly with IMAP.

I've tried a bunch of stuff to set TB up, but I always just keep getting the error message that "Thunderbird failed to find the settings for your email account." I've looked at the Mail Client Configuration page that says: Mail Server Username: contact+ukanuk.heliohost.org Incoming Mail Server: mail.ukanuk.heliohost.org Incoming Mail Server: (SSL) stevie.heliohost.org Outgoing Mail Server: mail.ukanuk.heliohost.org (server requires authentication) port 25 Outgoing Mail Server: (SSL) stevie.heliohost.org (server requires authentication) port 465 Supported Incoming Mail Protocols: POP3, POP3S (SSL/TLS), IMAP, IMAPS (SSL/TLS) Supported Outgoing Mail Protocols: SMTP, SMTPS (SSL/TLS) TB's fields don't quite exactly match up, but it seems like they are pretty close. My best guess for TB's boxes are: Your name (as shown to others): ukanuk Email address: contact@ukanuk.heliohost.org Password: (I can log into the webmail interface, so this is probably right) Incoming (IMAP): Server hostname: stevie.heliohost.org Port: Auto SSL: Autodetect Authentication: Normal password Outgoing (SMTP): Server hostname: stevie.heliohost.org Port: 465 SSL: Autodetect Authentication: Normal password Username: contact+ukanuk.heliohost.org I've also tried using mail.ukanuk.heliohost.org for my servers, but it still won't work. What am I doing wrong? Another interesting thing that might be related is that a test email message I sent to contact@ukanuk.heliohost.org never got through (I can log on with the web interface, but that's not nearly as nice as using TB).