skip to Main Content
Notifications
Clear all

After applying 1.10.13 I am unable to operate to the table via web browser if I connect via hostname

5 Posts
3 Users
0 Likes
3,991 Views
(@pawliger)
Contributor
Joined: 6 years ago
Posts: 12
Topic starter  

I applied the 1.10.13 update to my wood base table yesterday. Since then, I am unable to successfully operate the table via Chrome as I could before the update.  I try to connect to sisyphus.lan:3001 as I did before the update, but am faced with a Sisyphus-logo'd page with the message "Scanning for nearby tables... Connecting..." but nothing happens from there no matter how long I wait or times I refresh the page.

If instead I connect to the local IP address, as in 192.168.86.35:3001 I am able to then proceed as I used to and operate the table as expected. Of course the address may change over time, so would prefer to connect via local hostname.

Interestingly, the contents of the page served by accessing both by hostname and by IP are identical. The subresources like CSS and JS files work from both pages - I can both access  http://sisyphus.lan:3001/prod/styles.css and  http://192.168.86.35:3001/prod/styles.css so assume they can also be loaded from the page.

If I use Safari using http://sisyphus.lan:3001 I get further using the hostname, but arrive at the "No table found!" error page. I still have to use  http://192.168.86.35:3001 with Safari to actually operate the table.


   
Quote
(@bruce)
Admin
Joined: 6 years ago
Posts: 532
 

@pawliger - Thanks for the detailed report. I'm going to pass this along to Micah, who is most knowledgeable about connectivity issues. On occasion, I have run into table-name aliasing failing as well (with direct IP address working). Re-installing Bonjour print services and rebooting has fixed it for me (using a Win machine).

Bruce


   
ReplyQuote
(@pawliger)
Contributor
Joined: 6 years ago
Posts: 12
Topic starter  

Just applied 1.10.14 and still can't connect as sisyphus.lan:3001, still have to use the IP address. Is there an expected update?


   
ReplyQuote
(@micahr)
Admin
Joined: 6 years ago
Posts: 46
 

@pawliger - The correct URL is sisyphus.local:3001 not sisyphus.lan:3001

Thanks,

Micah


   
ReplyQuote
(@pawliger)
Contributor
Joined: 6 years ago
Posts: 12
Topic starter  

That worked. Interesting as .local doesn't resolve as I'd expect but works – maybe due to mDNS? Thanks!


   
ReplyQuote
Share:

We take your privacy seriously and will only use your personal information to provide you with the products and services you request from us. Please see our privacy policy for more details.

Back To Top
Search
    0
    Your Cart
    Your cart is emptyReturn to Shop