Edit Rename Changes History Upload Download Back to Top

Public Repository and Proxy Servers

The following advice is probably no longer relevant for most users. If you can't access the public repository due to firewall or proxy restrictions, try accessing it via port 80 or port 22. Simply replace the port number 5432 in the PostgreSQL environment string by 80 or 22.


If you can't get to the public repository due to firewall or proxy restrictions, the port of interest is 5432.

HI

Specific Solutions

If you have the MS Proxy Server blocking, here are the permissions to add under Winsock Proxy | Protocols

Protocol name: PostgreSQL
Initial Connection:
   Port: 5432
   Type: TCP
   Direction: Outbound
Port Ranges for subsequent connections:
   (none)

Tip of the hat to Steven Kelly.

Firewall generic Solutions

Under MS Windows you can use the tool HTTPort. This tool uses HTTP Tunneling to get your protocol through the firewall. You communicate with your localhost on a specified port which HTTPort translates to a remote host:port using public HTTHost. For some people the public HTTHost servers might be blocked by the firewall. In that case it's possible to run your own HTTHost server (also Windows tools :-()behind the firewall.

For the Public Repository in HTTPort you must add an entry with local port '5432' (hope you don't run your own PostgreSQL), remote host 'store.cincomsmalltalk.com' and remote port '5432'.

In Visualworks use the Store Database environment string: 'localhost_store_public'


Edit Rename Changes History Upload Download Back to Top