[BUG]Ubunut 22.04 AppImage 2.1.2 to Deckboard Pro on Android failed to connect.

I am using Deckboard Pro version 2.1.0 on Android (Samsung SM-P900 with Android Version 5.0.2)

Trying to connect via Wireless LAN, both machines are on the same subnet (192.168.12.0/24)

To Reproduce

Run Deckboard-2.1.2.AppImage on Ubuntu 22.04 LTS. (Launch, run as a program, Deckboard Loads OK with minimal board)
Scan the QR code and hit connect on the Android App, and got this message: Uh-oh! The Device can't connect to your computer. Please Try Again.

Expected behavior I expect Deckboard on the Android Tablet to show the Deckboard Board (as it used to in earlier versions of Deckboard)

Screenshots

Server App (please complete the following information):

OS: Ubuntu
- Version 22.04-LTS
- Firewall is disabled

Client App (please complete the following information):

OS: Android 5
Version 2.1.0

Required files

database.zip ng\Deckboard) Actually comes from /home/userid`/deckboard

Log file location unknown in Ubuntu

Additional context I've tried both with the Firewall on and off. When on the firewall is configured to allow ports 8500 and 4455 (OBS) from anywhere.

The deckboard appimage runs OK from Ubuntu itself and connects and operates OBS from the Ubuntu screen, but will not connect from ANY android device I have. (I've tried 4 different ones)

Output from netstat -tupln | grep deckboard

tcp6 0 0 :::8500 :::* LISTEN 907903/deckboard

It appears deckboard is only running on IPV6 and not on IPV4

I just confirmed the issue on Ubuntu distro. Feel free to try version 2.1.3-rc1

I just confirmed the issue on Ubuntu distro. Feel free to try version 2.1.3-rc1

Just tried this. The Netstat TUPLN is now showing the server is listening on port 8500 on IPV4, but the Pro client is still refusing to connect to the Server.

Where are the deckboard logs stored on Ubuntu? They might give more info, especially if I can alter the debugging level of deckboard server.

The USB connectivity is still working on the new version. it's just the WiFi. Again, I tried with and without a firewall. I've also checked the WiFi network and routes to ensure no other problems. I am able to get from the client tablet to the Server Ubuntu PC using other connections, such as HTML and Telnet (multiple non-standard ports)

Can you access http://127.0.0.1:8500/ through your browser and http://your.ip.address:8500 on your mobile device browser? It will show you a blank white page with Cannot GET / text, which, indicate the server is running as it should be.

And the log should be in ~/.config/deckboard/logs/log.log

On the local system I can see the Cannot GET / on browser. This works on both the loopback address (127.0.0.1) and the IP address of the machine.

However if I run the same from any other device (PC, Linux or Android device) I get no connection.

I know that there is no block in the network, because I can access other non-standard ports.

I have confirmed that there is no firewall blocking, and have run a port scan of the linux systems interface from the exterior and the other non-standard ports (that are advertised)b are not blocked. Only 8500 is not reporting.

I notice that the deckboard server is listening on all Addresses (0.0.0.0) at port 8500. Is there something in the configuration of either the Server or the Pro client that might prevent a connection?

On Wed, 15 Mar 2023 at 09:09, Riva Farabi @.***> wrote:

Can you access http://127.0.0.1:8500/ through your browser? It will show you a blank white page with Cannot GET / text, which, indicate the server is running as it should be.

And the log should be in ~/.config/deckboard/logs/log.log

— Reply to this email directly, view it on GitHub https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1469981514, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHEZVEDEMMH5BUMWYUPUJTW4G5RBANCNFSM6AAAAAAV2QTEEY . You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

Just to make sure. Did you tried accessing the said port through your mobile device's browser? And did the basic version of Deckboard app face the similar issue?

On Thu, Mar 16, 2023, 11:20 PM OldGitDoesTech @.***> wrote:

On the local system I can see the Cannot GET / on browser. This works on both the loopback address (127.0.0.1) and the IP address of the machine.

However if I run the same from any other device (PC, Linux or Android device) I get no connection.

I know that there is no block in the network, because I can access other non-standard ports.

I have confirmed that there is no firewall blocking, and have run a port scan of the linux systems interface from the exterior and the other non-standard ports (that are advertised)b are not blocked. Only 8500 is not reporting.

I notice that the deckboard server is listening on all Addresses (0.0.0.0) at port 8500. Is there something in the configuration of either the Server or the Pro client that might prevent a connection?

On Wed, 15 Mar 2023 at 09:09, Riva Farabi @.***> wrote:

Can you access http://127.0.0.1:8500/ through your browser? It will show you a blank white page with Cannot GET / text, which, indicate the server is running as it should be.

And the log should be in ~/.config/deckboard/logs/log.log

— Reply to this email directly, view it on GitHub < https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1469981514 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ACHEZVEDEMMH5BUMWYUPUJTW4G5RBANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

— Reply to this email directly, view it on GitHub https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1472289603, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBY5ZVGDEIHE2CXFFZUBHLW4M4U5ANCNFSM6AAAAAAV2QTEEY . You are receiving this because you commented.Message ID: @.***>

Yes,

Here's what I've done so far to test.

Server in Ubuntu 22.04, fully updated. LAN IP address is 192.168.12.101 WiFi Address is 192.168.12.52. Server allows connection and control directly from Deckboard. Client1 is Android 5 (Samsung), IP address is 192.168.12.50 (WiFi) Tried both Deckboard and DeckboardPro, both gave Uh-oh! Both connect via USB Client2 is Android 7 (Samsung), IP address is 192.168.12.65 (WiFi) Tried both Deckboard and DeckboardPro, both gave Uh-oh! Both connect via USB

I triple-checked the server and clients to ensure there is no firewall restrictions. I triple-checked the network router to ensure there were no blocks for the port and no port triggers.

I tried accessing the server through the mobile device browser. Both http://192.168.12.101:8500 and http://192.168.12.52:8500 It failed to connect. I tried to access the server through a browser on a different PC (I tried both Linux and Windows Laptops) Both http://192.168.12.101:8500 and http://192.168.12.52:8500 It failed to connect. I tried to access the server through a browser on the server itself, on Both http://192.168.12.101:8500 and http://192.168.12.52:8500 and http://127.0.0.1:8500 and it connected each time with the "Cannot GET /" message

I used nMAP to scan all ports including UDP (command: nMap -sU -p 1-65535 -T4 -A -v 192.168.12.101) (nMap Android on the Android devices)

I ran a port scanner on the server, it found port 8500. (result 8500/udp filtered fmtp) I ran a port scanner on the mobile device, pointed at the server, it found port 8500. (result 8500/udp filtered fmtp) I ran a port scanner on the other PCs (Linux and Windows), pointed at the server; it found port 8500. (result 8500/udp filtered fmtp)

It appears the server is displaying the port as a Flight Message Transport Protocol port on UDP.

I subsequently added a port trigger to the wifi router (NetGear RAX45 Nighthawk) to force allowing port 8500:UDP to be a trigger port from anywhere to anywhere and gave it a timeout of 3600 minutes, I got the same results with all tests.

Regards,

Len Inkster MBCS CITP Charted IT Professional Senior Security Consultant - EComSecSol Consultancy Inc.

On Thu, 16 Mar 2023 at 21:16, Riva Farabi @.***> wrote:

Just to make sure. Did you tried accessing the said port through your mobile device's browser? And did the basic version of Deckboard app face the similar issue?

On Thu, Mar 16, 2023, 11:20 PM OldGitDoesTech @.***> wrote:

On the local system I can see the Cannot GET / on browser. This works on both the loopback address (127.0.0.1) and the IP address of the machine.

However if I run the same from any other device (PC, Linux or Android device) I get no connection.

I know that there is no block in the network, because I can access other non-standard ports.

I have confirmed that there is no firewall blocking, and have run a port scan of the linux systems interface from the exterior and the other non-standard ports (that are advertised)b are not blocked. Only 8500 is not reporting.

I notice that the deckboard server is listening on all Addresses (0.0.0.0) at port 8500. Is there something in the configuration of either the Server or the Pro client that might prevent a connection?

On Wed, 15 Mar 2023 at 09:09, Riva Farabi @.***> wrote:

Can you access http://127.0.0.1:8500/ through your browser? It will show you a blank white page with Cannot GET / text, which, indicate the server is running as it should be.

And the log should be in ~/.config/deckboard/logs/log.log

— Reply to this email directly, view it on GitHub <

https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1469981514

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ACHEZVEDEMMH5BUMWYUPUJTW4G5RBANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

— Reply to this email directly, view it on GitHub < https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1472289603 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABBY5ZVGDEIHE2CXFFZUBHLW4M4U5ANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1472968942, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHEZVAOOJ5BAQS2IURPGCDW4O3O3ANCNFSM6AAAAAAV2QTEEY . You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

That's odd, the app service as FMTP is expected, but the app should be using TCP instead of UDP. Will run another test this weekend.

On Fri, 17 Mar 2023 at 22:53, OldGitDoesTech @.***> wrote:

Yes,

Here's what I've done so far to test.

Server in Ubuntu 22.04, fully updated. LAN IP address is 192.168.12.101 WiFi Address is 192.168.12.52. Server allows connection and control directly from Deckboard. Client1 is Android 5 (Samsung), IP address is 192.168.12.50 (WiFi) Tried both Deckboard and DeckboardPro, both gave Uh-oh! Both connect via USB Client2 is Android 7 (Samsung), IP address is 192.168.12.65 (WiFi) Tried both Deckboard and DeckboardPro, both gave Uh-oh! Both connect via USB

I triple-checked the server and clients to ensure there is no firewall restrictions. I triple-checked the network router to ensure there were no blocks for the port and no port triggers.

I tried accessing the server through the mobile device browser. Both http://192.168.12.101:8500 and http://192.168.12.52:8500 It failed to connect. I tried to access the server through a browser on a different PC (I tried both Linux and Windows Laptops) Both http://192.168.12.101:8500 and http://192.168.12.52:8500 It failed to connect. I tried to access the server through a browser on the server itself, on Both http://192.168.12.101:8500 and http://192.168.12.52:8500 and http://127.0.0.1:8500 and it connected each time with the "Cannot GET /" message

I used nMAP to scan all ports including UDP (command: nMap -sU -p 1-65535 -T4 -A -v 192.168.12.101) (nMap Android on the Android devices)

I ran a port scanner on the server, it found port 8500. (result 8500/udp filtered fmtp) I ran a port scanner on the mobile device, pointed at the server, it found port 8500. (result 8500/udp filtered fmtp) I ran a port scanner on the other PCs (Linux and Windows), pointed at the server; it found port 8500. (result 8500/udp filtered fmtp)

It appears the server is displaying the port as a Flight Message Transport Protocol port on UDP.

I subsequently added a port trigger to the wifi router (NetGear RAX45 Nighthawk) to force allowing port 8500:UDP to be a trigger port from anywhere to anywhere and gave it a timeout of 3600 minutes, I got the same results with all tests.

Regards,

Len Inkster MBCS CITP Charted IT Professional Senior Security Consultant - EComSecSol Consultancy Inc.

On Thu, 16 Mar 2023 at 21:16, Riva Farabi @.***> wrote:

Just to make sure. Did you tried accessing the said port through your mobile device's browser? And did the basic version of Deckboard app face the similar issue?

On Thu, Mar 16, 2023, 11:20 PM OldGitDoesTech @.***> wrote:

On the local system I can see the Cannot GET / on browser. This works on both the loopback address (127.0.0.1) and the IP address of the machine.

However if I run the same from any other device (PC, Linux or Android device) I get no connection.

I know that there is no block in the network, because I can access other non-standard ports.

I have confirmed that there is no firewall blocking, and have run a port scan of the linux systems interface from the exterior and the other non-standard ports (that are advertised)b are not blocked. Only 8500 is not reporting.

I notice that the deckboard server is listening on all Addresses (0.0.0.0) at port 8500. Is there something in the configuration of either the Server or the Pro client that might prevent a connection?

On Wed, 15 Mar 2023 at 09:09, Riva Farabi @.***> wrote:

Can you access http://127.0.0.1:8500/ through your browser? It will show you a blank white page with Cannot GET / text, which, indicate the server is running as it should be.

And the log should be in ~/.config/deckboard/logs/log.log

— Reply to this email directly, view it on GitHub <

https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1469981514

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ACHEZVEDEMMH5BUMWYUPUJTW4G5RBANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

— Reply to this email directly, view it on GitHub <

https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1472289603

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABBY5ZVGDEIHE2CXFFZUBHLW4M4U5ANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1472968942 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ACHEZVAOOJ5BAQS2IURPGCDW4O3O3ANCNFSM6AAAAAAV2QTEEY

. You are receiving this because you authored the thread.Message ID: @.***>

-- Len Inkster ISP ITCP IP3P Chartered IT Professional Certified IS Professional of Canada

— Reply to this email directly, view it on GitHub https://github.com/rivafarabi/deckboard/issues/968#issuecomment-1474048752, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBY5ZRMWTJIMAITUVHFCX3W4SCI5ANCNFSM6AAAAAAV2QTEEY . You are receiving this because you commented.Message ID: @.***>

This issue is stale because it has been open for 1 year with no activity.

This issue was closed because it has been inactive for 39 days since being marked as stale.

rivafarabi / deckboard

[BUG]Ubunut 22.04 AppImage 2.1.2 to Deckboard Pro on Android failed to connect. #968