Topic: Changing server mode

[janet]

JoshuaR

What does this give
config show SystemMode

[JoshuaR]

SystemMode=servergateway

(I have configured it in the right mode )

[janet]

JoshuaR

You could try this to see if it "fixes" your issues ie enables default settings
signal-event post-upgrade
reboot

If that doesn't resolve matters, then you need to issue db commands to enable public access for various services, and/or use the server manager to enable services.

config show |more
(then press space to scroll through the settings taking note as you go)

eg
config show httpd-e-smith

which will give something like

httpd-e-smith=service
    TCPPort=80
    access=public
    status=enabled

In your case I guess access=private

so do
config setprop httpd-e-smith access public

If status=disabled
You may also need to do
config setprop httpd-e-smith status enabled

and so on etc etc for all the other services you want to be publicly accessible, and enabled
and then do
signal-event post-upgrade
reboot

[JoshuaR]

httpd-e-smith=service
    TCPPort=80
    access=public
    status=enabled

In your case I guess access=private

Actually, it's set to public 

signal-event post-upgrade

just tried that, didn't seem to work


Thanks though.

[janet]

JoshuaR

signal-event post-upgrade

plus a reboot I hope.


So you have other issues then (firewall ???).
I suggest you post a bug at bugzilla, but search first as I seem to recall this issue has already been observed/reported. Report it again anyway.

[JoshuaR]

plus a reboot I hope.

signal-event post-upgrade; signal-event reboot
always

So you have other issues then (firewall ???).

I can only assume so.
I've been inclined to think it's because it's such an old install that's simply been upgraded over time.

I think if I get desperate I'll just do a clean install and try to find a way to transfer my contribs.

[JoshuaR]

This is really very embarrassing, but I thought since so many people posted to help me I owed it to them to post back with the result (also that and I'll probably never see any of you apart from on here  )

It was so simple, my ISP was blocking the inbound ports...I know that was one of the first suggested things to check, but since I have another site with the same ISP and exactly the same plan, I assumed they wouldn't be blocking the ports because they aren't at the other site...it turns out because I am a longer standing customer they included the port blocking 'feature' along with free AV etc...

Once again thanks to everyone who helped, and my apologies for wasting time such a noob mistake