Hi Boris,
I've noticed over the last few updates that the default IP port changes back to port 80 from what I have it set to.
Is there a way to make it so that this is preserved after these updates? Thanks.
Also when I change the port backand click SAVE the webpage just sits there and doesn't update. It will then timeout after a short while. (But the port does get changed)
Default changes to 80 after update ** solved **
Moderator: Mattk
Default changes to 80 after update ** solved **
Station: Davis Vantage Pro2 Plus
Hardware: Raspberry Pi 2 (Meteohub status)
Hardware: Raspberry Pi 2 (Meteohub status)
Re:Default changes to 80 after update
give 2.1c a try - it has some changes in the network handling.
I am still recovering from issues around how the new linux distro is handling the network configuration. As combinations what can be changed are broad, here and there still some hickups.
if 2.1c doesn't do the trick, you can also make use of the 2nd http-port 7777 which has been enabled as a second option (in case of emergency). So if the new port can be 7777 there is nothing to be changed, it is already there. This one is just configured to handle web administration. the new \"myweb\" folder cannot be served by it.
I am still recovering from issues around how the new linux distro is handling the network configuration. As combinations what can be changed are broad, here and there still some hickups.
if 2.1c doesn't do the trick, you can also make use of the 2nd http-port 7777 which has been enabled as a second option (in case of emergency). So if the new port can be 7777 there is nothing to be changed, it is already there. This one is just configured to handle web administration. the new \"myweb\" folder cannot be served by it.
Re:Default changes to 80 after update
Okay, that makes sense. Thanks.
I'm sure it's not easy trying to spend all of you time trying to fix every issue we find. I really appreciate the great amount of effort you've put into this product already. I really enjoy my meteohub and it's because of what you put into it. I look forward to using what it can do now and in the future. Thanks!
I'm sure it's not easy trying to spend all of you time trying to fix every issue we find. I really appreciate the great amount of effort you've put into this product already. I really enjoy my meteohub and it's because of what you put into it. I look forward to using what it can do now and in the future. Thanks!
Station: Davis Vantage Pro2 Plus
Hardware: Raspberry Pi 2 (Meteohub status)
Hardware: Raspberry Pi 2 (Meteohub status)
-
peteroi
- Senior Boarder

- Posts: 51
- Joined: Thu Jan 31, 2008 2:26 pm
- Location: Dietenheim / South Germany
- Contact:
Re:Default changes to 80 after update & myweb
Hi,
would it be possible to have a seperate defineable port for \"myweb\" - so that I could redirect my router directly to the myweb-space ? The router unfortunately does not allow to include subdir's...
Another problem with \"myweb\":
the manualstates:
\"Ï myweb enthält benutzerspezifische HTML-Dateien. Dies erlaubt Meteohub als individuellen
Webserver zu verwenden. Die index.html in diesem Verzeichnis wird über den HTTP-
Request \"http://..../myweb/index.html\" erreicht und ist mit dem Dashboard vorbelegt. Das
Sub-Verzeichnis \"uploads\" enthält Kopien der zum FTP-Upload bereitgestellten Daten. Im
Unterschied zum \"uploads\"-Verzeichnnis im vorangegangenen Absatz, werden die Daten
nach dem dem Upload nicht gelöscht, stehen also dauerhaft zur Verfügung. Die Idee dahinter
ist, dass diese Dateien von lokalen HTML Datei im \"myweb\"-Verzeichnis verwendet werden
können.\" ------------- would be perfect, but my upload-dir in myweb stays empty all the time !!!!
BR Peter
would it be possible to have a seperate defineable port for \"myweb\" - so that I could redirect my router directly to the myweb-space ? The router unfortunately does not allow to include subdir's...
Another problem with \"myweb\":
the manualstates:
\"Ï myweb enthält benutzerspezifische HTML-Dateien. Dies erlaubt Meteohub als individuellen
Webserver zu verwenden. Die index.html in diesem Verzeichnis wird über den HTTP-
Request \"http://..../myweb/index.html\" erreicht und ist mit dem Dashboard vorbelegt. Das
Sub-Verzeichnis \"uploads\" enthält Kopien der zum FTP-Upload bereitgestellten Daten. Im
Unterschied zum \"uploads\"-Verzeichnnis im vorangegangenen Absatz, werden die Daten
nach dem dem Upload nicht gelöscht, stehen also dauerhaft zur Verfügung. Die Idee dahinter
ist, dass diese Dateien von lokalen HTML Datei im \"myweb\"-Verzeichnis verwendet werden
können.\" ------------- would be perfect, but my upload-dir in myweb stays empty all the time !!!!
BR Peter
Pi/TE923
Re:Default changes to 80 after update **solved**
Hi,
mark the \"activate FTP upload\" checkbox in the ftp-settings on the push services page. it should do the trick.
according to the separate port... i will think about this.
mark the \"activate FTP upload\" checkbox in the ftp-settings on the push services page. it should do the trick.
according to the separate port... i will think about this.

